Displaying user interfaces associated with physical activities

ABSTRACT

The present disclosure generally relates to user interfaces and more specifically to techniques for displaying user interfaces associated with physical activities. Exemplary user interfaces related to activity competitions are described. Exemplary user interfaces related to a friends list for activity sharing are described. Exemplary user interfaces associated with alerts presented to a user in response to automatically determining a boundary of a workout are described. Exemplary user interfaces associated with configuring a pace alert for a workout application are described.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application No.62/679,906, entitled “DISPLAYING USER INTERFACES ASSOCIATED WITHPHYSICAL ACTIVITIES”, filed Jun. 3, 2018, and U.S. ProvisionalApplication No. 62/668,159, entitled “DISPLAYING USER INTERFACESASSOCIATED WITH PHYSICAL ACTIVITIES”, filed May 7, 2018, the entirecontents of which are hereby incorporated by reference.

FIELD

The present disclosure relates generally to user interfaces and morespecifically to techniques for displaying user interfaces associatedwith physical activities.

BACKGROUND

Many modern electronic devices provide the capability of trackingphysical activities by a user. Such electronic devices often displayinformation associated with the physical activities to the user. Sometechniques provide the ability to compare the physical activities of theuser with physical activities of other users. Other techniques providethe ability to begin and end tracking of a physical activity. Othertechniques provide the ability to set pace alerts for a physicalactivity. However, such techniques can be cumbersome and inefficient.

SUMMARY

Some techniques for displaying user interfaces associated with physicalactivities using electronic devices are generally cumbersome andinefficient. For example, some existing techniques use a complex andtime-consuming user interface, which may include multiple key presses orkeystrokes. Existing techniques require more time than necessary,wasting user time and device energy. This latter consideration isparticularly important in battery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for displaying userinterfaces associated with physical activities. Such methods andinterfaces optionally complement or replace other methods for displayinguser interfaces associated with physical activities. Such methods andinterfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges.

A system of one or more computers can be configured to performparticular operations or actions by virtue of having software, firmware,hardware, or a combination of them installed on the system that inoperation causes or cause the system to perform the actions. One or morecomputer programs can be configured to perform particular operations oractions by virtue of including instructions that, when executed by dataprocessing apparatus, cause the apparatus to perform the actions.

One general aspect includes a method performed at an electronic deviceincluding a display. The method includes receiving first user activitydata for a time period, the first user activity data including at leastfirst user activity data for a first time subset and first user activitydata for a second time subset. The method further includes receivingsecond user activity data for the time period, the second user activitydata including at least second user activity data for the first timesubset and second user activity data for the second time subset. Themethod further includes displaying, on the display, a user interfaceincluding: (1) a representation of the first user activity data for thefirst time subset; (2) a representation of the first user activity datafor the second time subset; (3) a cumulative representation of the firstuser activity data for the time period, where the cumulativerepresentation of the first user activity data for the time period isbased on at least the first user activity data for a first time subsetand the first user activity data for a second time subset; (4) arepresentation of the second user activity data for the first timesubset; (5) a representation of the second user activity data for thesecond time subset; and (6) a cumulative representation of the seconduser activity data for the time period, where the cumulativerepresentation of the second user activity data for the time period isbased on at least the second user activity data for a first time subsetand the second user activity data for a second time subset. Otherexamples of this aspect include corresponding computer systems,apparatus, and computer programs recorded on one or more computerstorage devices, each configured to perform the actions of the methods.

One general aspect includes a method performed at an electronic deviceincluding a display. The method includes receiving first user activitydata for a first user, where the first user activity data corresponds toa first time period and a second time period. The method furtherincludes receiving second user activity data for a second user, wherethe second user activity data corresponds to the first time period, andwhere the first time period includes a first elapsed sub-period and afirst unelapsed sub-period for an activity competition between the firstuser and the second user. The method further includes receiving thirduser activity data for the third user, where the third user activitydata corresponds to the second time period, and where the second timeperiod includes a second elapsed sub-period and a second unelapsedsub-period for an activity competition between the first user and thethird user. The method further includes displaying, on the display, auser interface including: (1) a representation of the first useractivity data and the second user activity data during the first elapsedsub-period for the activity competition between the first user and thesecond user; (2) an indication of an amount of time in the firstunelapsed sub-period for the activity competition between the first userand the second user; (3) a representation of the first activity data andthe third activity data during the second elapsed sub-period for theactivity competition between the first user and the third user; and (4)an indication of an amount of time in the second unelapsed sub-periodfor the activity competition between the first user and the third user.Other examples of this aspect include corresponding computer systems,apparatus, and computer programs recorded on one or more computerstorage devices, each configured to perform the actions of the methods.

One general aspect includes a method performed at an electronic deviceincluding a display and one or more sensors. The method includesdetecting, via the one or more sensors, activity data. The methodfurther includes, in response to detecting the activity data and inaccordance with a determination that the activity data satisfiesactivity boundary alert criteria, displaying an activity boundary alert.The method further includes, in further response to detecting theactivity data and in accordance with a determination that the activitydata does not satisfy the activity boundary alert criteria, forgoingdisplay of the activity boundary alert. Other examples of this aspectinclude corresponding computer systems, apparatus, and computer programsrecorded on one or more computer storage devices, each configured toperform the actions of the methods.

One general aspect includes a method performed at an electronic device.The method includes displaying a physical activity rate user interfaceincluding a first setting affordance and a second setting affordance.The method further includes. while displaying the physical activity rateuser interface, receiving a first user input. The method furtherincludes, in response to receiving the first user input and inaccordance with the first user input corresponding to selection of thefirst setting affordance, configuring a physical activity ratecalculation to use a first portion of a dataset. The method furtherincludes, in response to receiving the first user input and inaccordance with the first user input corresponding to selection of thesecond setting affordance, configuring a physical activity ratecalculation to use a second portion of the dataset different from thefirst portion. Other examples of this aspect include correspondingcomputer systems, apparatus, and computer programs recorded on one ormore computer storage devices, each configured to perform the actions ofthe methods.

One general aspect includes a non-transitory computer-readable storagemedium storing one or more programs configured to be executed by one ormore processors of an electronic device with a display, the one or moreprograms including instructions for any of the methods described above.

One general aspect includes a transitory computer-readable storagemedium storing one or more programs configured to be executed by one ormore processors of an electronic device with a display, the one or moreprograms including instructions for any of the methods described above.

One general aspect includes an electronic device, including a display.The electronic device also includes one or more processors. Theelectronic device also includes memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for performing any of the methodsdescribed above.

One general aspect includes an electronic device, including a display.The electronic device also includes means for receiving first useractivity data for a time period, the first user activity data includingat least first user activity data for a first time subset and first useractivity data for a second time subset. The electronic device alsoincludes means for receiving second user activity data for the timeperiod, the second user activity data including at least second useractivity data for the first time subset and second user activity datafor the second time subset. The electronic device also includes meansfor displaying, on the display, a user interface including: (1) arepresentation of the first user activity data for the first timesubset; (2) a representation of the first user activity data for thesecond time subset; (3) a cumulative representation of the first useractivity data for the time period, where the cumulative representationof the first user activity data for the time period is based on at leastthe first user activity data for a first time subset and the first useractivity data for a second time subset; (4) a representation of thesecond user activity data for the first time subset; (5) arepresentation of the second user activity data for the second timesubset; (6) and a cumulative representation of the second user activitydata for the time period, where the cumulative representation of thesecond user activity data for the time period is based on at least thesecond user activity data for a first time subset and the second useractivity data for a second time subset.

One general aspect includes an electronic device, including a display.The electronic device also includes means for receiving first useractivity data for a first user, where the first user activity datacorresponds to a first time period and a second time period. Theelectronic device also includes means for receiving second user activitydata for a second user, where the second user activity data correspondsto the first time period, and where the first time period includes afirst elapsed sub-period and a first unelapsed sub-period for anactivity competition between the first user and the second user. Theelectronic device also includes means for receiving third user activitydata for the third user, where the third user activity data correspondsto the second time period, and where the second time period includes asecond elapsed sub-period and a second unelapsed sub-period for anactivity competition between the first user and the third user. Theelectronic device also includes means for displaying, on the display, auser interface including: (1) a representation of the first useractivity data and the second user activity data during the first elapsedsub-period for the activity competition between the first user and thesecond user; (2) an indication of an amount of time in the firstunelapsed sub-period for the activity competition between the first userand the second user; (3) a representation of the first activity data andthe third activity data during the second elapsed sub-period for theactivity competition between the first user and the third user; and (4)an indication of an amount of time in the second unelapsed sub-periodfor the activity competition between the first user and the third user.

One general aspect includes an electronic device, including a display.The electronic device also includes means for detecting, via the one ormore sensors, activity data. The electronic device also includes a meansfor, in response to detecting the activity data and in accordance with adetermination that the activity data satisfies activity boundary alertcriteria, displaying an activity boundary alert. The electronic devicealso includes a means for, in response to detecting the activity dataand in accordance with a determination that the activity data does notsatisfy the activity boundary alert criteria, forgoing display of theactivity boundary alert.

One general aspect includes an electronic device, including a display.The electronic device also includes means for displaying a physicalactivity rate user interface including a first setting affordance and asecond setting affordance. The electronic device also includes meansfor, while displaying the physical activity rate user interface,receiving a first user input. The electronic device also includes meansfor, in response to receiving the first user input and in accordancewith the first user input corresponding to selection of the firstsetting affordance, configuring a physical activity rate calculation touse a first portion of a dataset. The electronic device also includesmeans for, in response to receiving the first user input and inaccordance with the first user input corresponding to selection of thesecond setting affordance, configuring a physical activity ratecalculation to use a second portion of the dataset different from thefirst portion.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for displaying user interfaces associated with physicalactivities, thereby increasing the effectiveness, efficiency, and usersatisfaction with such devices. Such methods and interfaces maycomplement or replace other methods for displaying user interfacesassociated with physical activities.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described examples, referenceshould be made to the Description of Examples below, in conjunction withthe following drawings in which like reference numerals refer tocorresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some examples.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some examples.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some examples.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with some examples.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someexamples.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some examples.

FIG. 5A illustrates a personal electronic device in accordance with someexamples.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some examples.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some examples.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some examples.

FIGS. 6A-6T illustrate exemplary user interfaces related to activitycompetitions in accordance with some examples.

FIGS. 7A-7B is a flow diagram illustrating a method for displaying anactivity competition representation using an electronic device inaccordance with some examples.

FIGS. 8A-8Y illustrate exemplary user interfaces related to a friendslist for activity sharing in accordance with some examples.

FIGS. 9A-9B is a flow diagram illustrating a method for displaying afriends list representation using an electronic device in accordancewith some examples.

FIGS. 10A-10Q illustrate exemplary user interfaces associated withalerts presented to a user in response to automatically determining aboundary of a workout in accordance with some examples.

FIG. 11 is a flow diagram illustrating a method for displaying an alertin response to automatically determining a boundary of physical activityusing an electronic device in accordance with some examples.

FIGS. 12A-12AK illustrate exemplary user interfaces associated withconfiguring a pace alert for a workout application in accordance withsome examples.

FIG. 13 is a flow diagram illustrating a method for displaying a userinterface to configure a dataset that is used to calculate a pace usingan electronic device in accordance with some examples.

DESCRIPTION OF EXAMPLES

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary examples.

There is a need for electronic devices that provide efficient methodsand interfaces for displaying user interfaces associated with physicalactivities. Such techniques can reduce the cognitive burden on a userwho accesses user interfaces associated with physical activities,thereby enhancing productivity. Further, such techniques can reduceprocessor and battery power otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for managing eventnotifications. FIGS. 6A-6T illustrate exemplary user interfaces relatedto activity competitions in accordance with some examples. FIGS. 7A-7Bis a flow diagram illustrating a method for displaying an activitycompetition representation using an electronic device in accordance withsome examples. The user interfaces in FIGS. 6A-6T are used to illustratethe processes described below, including the process in FIGS. 7A-7B.FIGS. 8A-8Y illustrate exemplary user interfaces related to a friendslist for activity sharing in accordance with some examples. FIGS. 9A-9Bis a flow diagram illustrating a method for displaying a friends listrepresentation using an electronic device in accordance with someexamples. The user interfaces in FIGS. 8A-8Y are used to illustrate theprocesses described below, including the process in FIGS. 9A-9B. FIGS.10A-10Q illustrate exemplary user interfaces associated with alertspresented to a user in response to automatically determining a boundaryof a workout in accordance with some examples. FIG. 11 is a flow diagramillustrating a method for displaying an alert in response toautomatically determining a boundary of physical activity using anelectronic device in accordance with some examples. The user interfacesin FIGS. 10A-10Q are used to illustrate the processes described below,including the process in FIG. 11. FIGS. 12A-12AK illustrate exemplaryuser interfaces associated with configuring a pace alert for a workoutapplication in accordance with some examples. FIG. 13 is a flow diagramillustrating a method for displaying a user interface to configure adataset that is used to calculate a pace using an electronic device inaccordance with some examples. The user interfaces in FIGS. 12A-12AK areused to illustrate the processes described below, including the processin FIG. 13.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described examples. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedexamples herein is for the purpose of describing particular examplesonly and is not intended to be limiting. As used in the description ofthe various described examples and the appended claims, the singularforms “a,” “an,” and “the” are intended to include the plural forms aswell, unless the context clearly indicates otherwise. It will also beunderstood that the term “and/or” as used herein refers to andencompasses any and all possible combinations of one or more of theassociated listed items. It will be further understood that the terms“includes,” “including,” “comprises,” and/or “comprising,” when used inthis specification, specify the presence of stated features, integers,steps, operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Examples of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someexamples, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary examples of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in some examples,the device is not a portable communications device, but is a desktopcomputer with a touch-sensitive surface (e.g., a touch screen displayand/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward examples of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some examples. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some examples, peripherals interface118, CPU 120, and memory controller 122 are, optionally, implemented ona single chip, such as chip 104. In some other examples, they are,optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some examples, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateexamples, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some examples, some or all of thevisual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryexample, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other examples. Touch screen 112 and display controller 156optionally detect contact and any movement or breaking thereof using anyof a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary example, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some examples of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some examples of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some examples, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some examples, the user interface is designedto work primarily with finger-based contacts and gestures, which can beless precise than stylus-based input due to the larger area of contactof a finger on the touch screen. In some examples, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some examples, in addition to the touch screen, device 100 optionallyincludes a touchpad (not shown) for activating or deactivatingparticular functions. In some examples, the touchpad is atouch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some examples, an optical sensor islocated on the back of device 100, opposite touch screen display 112 onthe front of the device so that the touch screen display is enabled foruse as a viewfinder for still and/or video image acquisition. In someexamples, an optical sensor is located on the front of the device sothat the user's image is, optionally, obtained for video conferencingwhile the user views the other video conference participants on thetouch screen display. In some examples, the position of optical sensor164 can be changed by the user (e.g., by rotating the lens and thesensor in the device housing) so that a single optical sensor 164 isused along with the touch screen display for both video conferencing andstill and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some examples, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some examples, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some examples, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some examples, at least one tactile output generatoris collocated with, or proximate to, a touch-sensitive surface (e.g.,touch-sensitive display system 112) and, optionally, generates a tactileoutput by moving the touch-sensitive surface vertically (e.g., in/out ofa surface of device 100) or laterally (e.g., back and forth in the sameplane as a surface of device 100). In some examples, at least onetactile output generator sensor is located on the back of device 100,opposite touch screen display 112, which is located on the front ofdevice 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome examples, information is displayed on the touch screen display in aportrait view or a landscape view based on an analysis of data receivedfrom the one or more accelerometers. Device 100 optionally includes, inaddition to accelerometer(s) 168, a magnetometer (not shown) and a GPS(or GLONASS or other global navigation system) receiver (not shown) forobtaining information concerning the location and orientation (e.g.,portrait or landscape) of device 100.

In some examples, the software components stored in memory 102 includeoperating system 126, communication module (or set of instructions) 128,contact/motion module (or set of instructions) 130, graphics module (orset of instructions) 132, text input module (or set of instructions)134, Global Positioning System (GPS) module (or set of instructions)135, and applications (or sets of instructions) 136. Furthermore, insome examples, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device/globalinternal state 157, as shown in FIGS. 1A and 3. Device/global internalstate 157 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch screen display 112; sensor state, including informationobtained from the device's various sensors and input control devices116; and location information concerning the device's location and/orattitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome examples, the external port is a multi-pin (e.g., 30-pin) connectorthat is the same as, or similar to and/or compatible with, the 30-pinconnector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some examples, contact/motionmodule 130 and display controller 156 detect contact on a touchpad.

In some examples, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some examples, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some examples, graphics module 132 stores data representing graphicsto be used. Each graphic is, optionally, assigned a corresponding code.Graphics module 132 receives, from applications etc., one or more codesspecifying graphics to be displayed along with, if necessary, coordinatedata and other graphic property data, and then generates screen imagedata to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some examples, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some examples, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In some examples,a widget includes an XML (Extensible Markup Language) file and aJavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some examples, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some examples,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various examples. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someexamples, memory 102 optionally stores a subset of the modules and datastructures identified above. Furthermore, memory 102 optionally storesadditional modules and data structures not described above.

In some examples, device 100 is a device where operation of a predefinedset of functions on the device is performed exclusively through a touchscreen and/or a touchpad. By using a touch screen and/or a touchpad asthe primary input control device for operation of device 100, the numberof physical input control devices (such as push buttons, dials, and thelike) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some examples, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such examples, a “menubutton” is implemented using a touchpad. In some other examples, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some examples. In some examples, memory 102(FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., in operatingsystem 126) and a respective application 136-1 (e.g., any of theaforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some examples,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someexamples, device/global internal state 157 is used by event sorter 170to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some examples, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some examples, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other examples,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some examples, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some examples, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other examples, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other examples, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In examples including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some examples,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some examples, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherexamples, event sorter 170 is a stand-alone module, or a part of anothermodule stored in memory 102, such as contact/motion module 130.

In some examples, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other examples, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some examples, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someexamples, one or more of data updater 176, object updater 177, and GUIupdater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some examples, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some examples, events include rotation of the device fromone orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some examples, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some examples, sub-events in anevent (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some examples, theevent also includes information for one or more associated eventhandlers 190.

In some examples, event definition 187 includes a definition of an eventfor a respective user-interface object. In some examples, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some examples, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some examples, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some examples, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome examples, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some examples, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some examples, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some examples, event recognizer 180 throws a flag associated with therecognized event, and event handler 190 associated with the flag catchesthe flag and performs a predefined process.

In some examples, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some examples, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some examples, object updater 177 creates and updatesobjects used in application 136-1. For example, object updater 177creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some examples, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In some examples,data updater 176, object updater 177, and GUI updater 178 are includedin a single module of a respective application 136-1 or application view191. In other examples, they are included in two or more softwaremodules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some examples. The touch screen optionallydisplays one or more graphics within user interface (UI) 200. In thisexample, as well as others described below, a user is enabled to selectone or more of the graphics by making a gesture on the graphics, forexample, with one or more fingers 202 (not drawn to scale in the figure)or one or more styluses 203 (not drawn to scale in the figure). In someexamples, selection of one or more graphics occurs when the user breakscontact with the one or more graphics. In some examples, the gestureoptionally includes one or more taps, one or more swipes (from left toright, right to left, upward and/or downward), and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some implementations orcircumstances, inadvertent contact with a graphic does not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon optionally does not select the corresponding application when thegesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some examples, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some examples, device 100 includes touch screen 112, menu button 204,push button 206 for powering the device on/off and locking the device,volume adjustment button(s) 208, subscriber identity module (SIM) cardslot 210, headset jack 212, and docking/charging external port 124. Pushbutton 206 is, optionally, used to turn the power on/off on the deviceby depressing the button and holding the button in the depressed statefor a predefined time interval; to lock the device by depressing thebutton and releasing the button before the predefined time interval haselapsed; and/or to unlock the device or initiate an unlock process. Inan alternative example, device 100 also accepts verbal input foractivation or deactivation of some functions through microphone 113.Device 100 also, optionally, includes one or more contact intensitysensors 165 for detecting intensity of contacts on touch screen 112and/or one or more tactile output generators 167 for generating tactileoutputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with some examples.Device 300 need not be portable. In some examples, device 300 is alaptop computer, a desktop computer, a tablet computer, a multimediaplayer device, a navigation device, an educational device (such as achild's learning toy), a gaming system, or a control device (e.g., ahome or industrial controller). Device 300 typically includes one ormore processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some examples, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various examples. In some examples, memory 370 optionallystores a subset of the modules and data structures identified above.Furthermore, memory 370 optionally stores additional modules and datastructures not described above.

Attention is now directed towards examples of user interfaces that are,optionally, implemented on, for example, portable multifunction device100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome examples. Similar user interfaces are, optionally, implemented ondevice 300. In some examples, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some examples, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someexamples, a label for a particular application icon is distinct from aname of an application corresponding to the particular application icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some examples, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some examples, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these examples, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in some examples,one or more of the finger inputs are replaced with input from anotherinput device (e.g., a mouse-based input or stylus input). For example, aswipe gesture is, optionally, replaced with a mouse click (e.g., insteadof a contact) followed by movement of the cursor along the path of theswipe (e.g., instead of movement of the contact). As another example, atap gesture is, optionally, replaced with a mouse click while the cursoris located over the location of the tap gesture (e.g., instead ofdetection of the contact followed by ceasing to detect the contact).Similarly, when multiple user inputs are simultaneously detected, itshould be understood that multiple computer mice are, optionally, usedsimultaneously, or a mouse and finger contacts are, optionally, usedsimultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some examples, device 500 can include some or allof the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some examples, device 500 has touch-sensitive displayscreen 504, hereafter touch screen 504. Alternatively, or in addition totouch screen 504, device 500 has a display and a touch-sensitivesurface. As with devices 100 and 300, in some examples, touch screen 504(or the touch-sensitive surface) optionally includes one or moreintensity sensors for detecting intensity of contacts (e.g., touches)being applied. The one or more intensity sensors of touch screen 504 (orthe touch-sensitive surface) can provide output data that represents theintensity of touches. The user interface of device 500 can respond totouches based on their intensity, meaning that touches of differentintensities can invoke different user interface operations on device500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some examples, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some examples, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someexamples, device 500 can include some or all of the components describedwith respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512 thatoperatively couples I/O section 514 with one or more computer processors516 and memory 518. I/O section 514 can be connected to display 504,which can have touch-sensitive component 522 and, optionally, intensitysensor 524 (e.g., contact intensity sensor). In addition, I/O section514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 is, optionally, a rotatable input device or adepressible and rotatable input device, for example. Input mechanism 508is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700(FIGS. 7A-7B), 900 (FIGS. 9A-9B), 1100 (FIG. 11), and 1300 (FIG. 13). Acomputer-readable storage medium can be any medium that can tangiblycontain or store computer-executable instructions for use by or inconnection with the instruction execution system, apparatus, or device.In some examples, the storage medium is a transitory computer-readablestorage medium. In some examples, the storage medium is a non-transitorycomputer-readable storage medium. The non-transitory computer-readablestorage medium can include, but is not limited to, magnetic, optical,and/or semiconductor storages. Examples of such storage include magneticdisks, optical discs based on CD, DVD, or Blu-ray technologies, as wellas persistent solid-state memory such as flash, solid-state drives, andthe like. Personal electronic device 500 is not limited to thecomponents and configuration of FIG. 5B, but can include other oradditional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some examples, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some examples, the durationof the contact is used in determining the characteristic intensity(e.g., when the characteristic intensity is an average of the intensityof the contact over time). In some examples, the characteristicintensity is compared to a set of one or more intensity thresholds todetermine whether an operation has been performed by a user. Forexample, the set of one or more intensity thresholds optionally includesa first intensity threshold and a second intensity threshold. In thisexample, a contact with a characteristic intensity that does not exceedthe first threshold results in a first operation, a contact with acharacteristic intensity that exceeds the first intensity threshold anddoes not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some examples, acomparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some examples, each contact is assigned a respectiveintensity that is a portion of the aggregate intensity. FIG. 5Dillustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some examples, a characteristicintensity of a contact is based on one or more intensities of thecontact. In some examples, the intensity sensors are used to determine asingle characteristic intensity (e.g., a single characteristic intensityof a single contact). It should be noted that the intensity diagrams arenot part of a displayed user interface, but are included in FIGS. 5C-5Dto aid the reader.

In some examples, a portion of a gesture is identified for purposes ofdetermining a characteristic intensity. For example, a touch-sensitivesurface optionally receives a continuous swipe contact transitioningfrom a start location and reaching an end location, at which point theintensity of the contact increases. In this example, the characteristicintensity of the contact at the end location is, optionally, based ononly a portion of the continuous swipe contact, and not the entire swipecontact (e.g., only the portion of the swipe contact at the endlocation). In some examples, a smoothing algorithm is, optionally,applied to the intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some examples, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some examples, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In some examples,when a contact is detected with a characteristic intensity below thelight press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some examples, the contact-detection intensity threshold is zero. Insome examples, the contact-detection intensity threshold is greater thanzero.

In some examples described herein, one or more operations are performedin response to detecting a gesture that includes a respective pressinput or in response to detecting the respective press input performedwith a respective contact (or a plurality of contacts), where therespective press input is detected based at least in part on detectingan increase in intensity of the contact (or plurality of contacts) abovea press-input intensity threshold. In some examples, the respectiveoperation is performed in response to detecting the increase inintensity of the respective contact above the press-input intensitythreshold (e.g., a “down stroke” of the respective press input). In someexamples, the press input includes an increase in intensity of therespective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the press-inputintensity threshold, and the respective operation is performed inresponse to detecting the subsequent decrease in intensity of therespective contact below the press-input threshold (e.g., an “up stroke”of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “ITL”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“ITD”) in FIG. 5H. The gesture performed with contact 562 is detected ontouch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some examples, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “ITD”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “ITD”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome examples, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some examples, the display of representations 578A-578C includes ananimation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some examples, the animationprogresses in accordance with an intensity of contact 562, as shown inFIGS. 5F-5G, where the representations 578A-578C appear and move upwardsas the intensity of contact 562 increases toward the deep pressintensity threshold (e.g., “ITD”). In some examples, the intensity, onwhich the progress of the animation is based, is the characteristicintensity of the contact. The operations described with reference toFIGS. 5E-5H can be performed using an electronic device similar oridentical to device 100, 300, or 500.

In some examples, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome examples, the press input includes an increase in intensity of therespective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some examples, the press input isdetected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some examples, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards examples of user interfaces (“UI”) andassociated processes that are implemented on an electronic device, suchas portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6T illustrate exemplary user interfaces related to activitycompetitions in accordance with some examples. Such activitycompetitions allow participants of the activity competitions to competefor a set time period using physical activity detected by theirrespective devices. For example, an activity competitions can beconfigured to last for a week. During the week, devices of participantscan detect physical activity performed by the participants. By the endof the week, the participant with the most detected physical activitycan win the activity competition. In some examples, an activitycompetition can be between two participants. In other examples, anactivity competition can be between more than two participants.

FIG. 6A depicts two electronic devices (i.e., device 600A and device600B). For explanatory purposes, device 600A will belong to Molly anddevice 600B will belong to Aled; the two devices are in electroniccommunication (e.g., wireless communication). Each of the two electronicdevices can include a touch-sensitive display (e.g., touch-sensitivedisplay 602A and touch-sensitive display 602B) for displaying userinterfaces that can be interacted with by touching the touch-sensitivedisplay. It should be recognized that other input mechanisms (other thantouch) can be used to interact with the user interfaces displayed by thetwo electronic devices. For example, each electronic device includes arotatable input mechanism (e.g., rotatable input mechanism 604A androtatable input mechanism 604B that can each rotate with respect to thehousings of the respective devices) and a push button (e.g., push button606A and push button 606B). In some examples, devices 600A and 600B mayinclude one or more features of devices 100, 300, or 500, as describedabove. When multiple electronic devices are illustrated in a singlefigure, it should be recognized that the user interfaces depicted in thefigure can be synced in time (e.g., while device 600A displays a firstuser interface in a figure, device 600B displays a second user interfacein the figure).

Referring to device 600A in FIG. 6A, user interface 608 is displayed ontouch-sensitive display 602A. User interface 608 is a notification thatis displayed in response to a determination that a participant of theactivity competition (e.g., Molly) associated with device 600A hascompleted three different physical activity goals (referred to asrings). A representation of the three different physical activity goalscompleted is illustrated at representation 610B.

Referring to device 600B in FIG. 6A, user interface 612 is displayed inresponse to receiving data, transmitted from device 600A, indicatingthat Molly completed her three different physical activity goals. Forexample, user interface 612 can be informing Aled that Molly completedher three different physical activity goals (as illustrated atrepresentation 610A). It should be recognized that user interface 612can be displayed in response to other physical activity performed byMolly, such as Molly completing a workout.

User interface 612 can include a scrollable list of affordances 614,where each affordance is associated with a different operation. Forexample, the scrollable list of affordances 614 includes firstaffordance 614A, second affordance 614B, and third affordance 614C.Selection of first affordance 614A can initiate a sequence to begin anactivity competition between Aled and Molly. Selection of secondaffordance 614B can cause a messaging interface to be displayed (asdepicted in FIG. 6J and discussed below) to allow Aled to send a messageto Molly in response to her completing her three physical activitygoals. Selection of third affordance 614 can cause device 600B to ceaseto display user interface 612. In FIG. 6A, the full content of userinterface 612 is shown, including portions that would not initially fiton the display (e.g., portions accessed via scrolling), for ease ofexplanation. Throughout the disclosure, additional user interfaces areshown in this manner for ease of explanation.

FIG. 6B again illustrates the user interfaces depicted in FIG. 6A. Whiledevice 600A is continuing to display user interface 608 in FIG. 6B, itshould be recognized that device 600A can display a different userinterface. As described above, user interface 612 on device 600Bincludes first affordance 614A. Referring to FIG. 6B, user input (e.g.,tap input) 601 is received, where user input 601 corresponds toselection of first affordance 614A. In accordance with a determinationthat user input 601 is detected at first affordance 614A, a userinterface related to initiating an activity competition is displayed(e.g., user interface 616 depicted in FIG. 6C).

Referring to FIG. 6C, user interface 616 is displayed on touch-sensitivedisplay 602B in response to selection of first affordance 614A. Userinterface 616 describes rules for an activity competition. It should berecognized that, in some examples, user interface 616 might not bedisplayed in response to selection of first affordance 614A (as depictedin FIG. 6B). For example, Aled might have already initiated a particularnumber of activity competitions such that a user interface describingrules for an activity competition is not necessary. In some examples,user interface 616 can be displayed in response to selection of firstaffordance 614A for a particular number of times per participant. Forexample, user interface 616 can be displayed to Aled 2 times before itis no longer displayed to Aled.

User interface 616 includes icon 618. Icon 618 can represent activitycompetitions between Molly and Aled, such that all activity competitions(e.g., past activity competitions) between Molly and Aled are associatedwith icon 618. In some examples, activity competitions between differentparticipants (such as Molly and Steve) can be represented by differenticons with different visual themes than icon 618. It should berecognized that, in some examples, icons can be assigned to activitycompetitions prior to display of user interface 616. User interface 616further includes affordance 620 for indicating an acceptance of theterms in user interface 616 and causing an invitation to begin anactivity competition to be sent to Molly (e.g., to device 600A).

FIG. 6D again illustrates the user interfaces depicted in FIG. 6C. Whiledevice 600A is continuing to display user interface 608 in FIG. 6D, itshould be recognized that device 600A can display a different userinterface. As described above, user interface 616 includes an affordance620A. Referring to FIG. 6D, user input (e.g., tap input) 603 isreceived, where user input 603 corresponds to selection of affordance620. In accordance with a determination that user input 603 is detectedat affordance 620, an invitation for an activity competition betweenAled and Molly can be sent to device 600A (as depicted in FIG. 6E).

Referring to FIG. 6E, in response to Molly selecting affordance 620 inuser interface 616 (as depicted in FIG. 6D), user interface 628 can bedisplayed on device 600B and user interface 622 can be displayed ondevice 600A. User interface 628 indicates that Aled must wait for Mollyto accept the invitation sent by Aled, before the activity competitionwill start. User interface 628 includes icon 630 (which can have thesame theme as icon 618, as depicted in FIG. 6C) and affordance 632, tocease to display user interface 628.

User interface 622 of device 600A describes rules for an activitycompetition, similar to user interface 616. User interface 622 includesicon 624 (which can have the same theme as icon 618, as depicted in FIG.6C). User interface 622 further includes a scrollable list ofaffordances 626, where each affordance is associated with a differentoperation. For example, the scrollable list of affordances 626 includesfirst affordance 626A and second affordance 626B.

Selection of first affordance 626A can accept the invitation for theactivity competition sent by Aled. Acceptance of the invitation cancause the activity competition to begin at a predefined time after theselection (e.g., midnight of the current day), as further describedbelow. Selection of second affordance 626B can cause device 600B toreject the invitation (e.g., cause the activity competition to notbegin) and cease to display user interface 612.

FIG. 6F again illustrates the user interfaces depicted in FIG. 6E. Whiledevice 600B is continuing to display user interface 628 in FIG. 6F, itshould be recognized that device 600B can display a different userinterface. As described above, user interface 622 on device 600Aincludes first affordance 626A. Referring to FIG. 6F, user input (e.g.,tap input) 605 is received, where user input 605 corresponds toselection of first affordance 626A. In accordance with a determinationthat user input 605 is detected at first affordance 626A, an activitycompetition between Molly and Aled can be set to initiate at apredefined time in the future.

Referring to FIG. 6G, in response to receiving the selection (e.g., byMolly) of affordance 605 in user interface 622 (as depicted in FIG. 6F),user interface 634 can be displayed on device 600A and user interface640 can be displayed on device 600B. User interface 634 indicates thatthe activity competition with Aled will start tomorrow. User interface634 includes icon 636 (which can have the same theme as icon 618, asdepicted in FIG. 6C) and affordance 638, to cease to display userinterface 638.

User interface 640 indicates that the invitation that Aled sent wasaccepted and that the activity competition with Molly will starttomorrow. User interface 640 includes icon 642 (which can have the sametheme as icon 618, as depicted in FIG. 6C). User interface 622 furtherincludes a scrollable list of affordances 644, where each affordance isassociated with a different operation. For example, the scrollable listof affordances 626 includes first affordance 626A for displaying amessaging user interface (as depicted in FIG. 6I) and second affordance626B for ceasing to display user interface 640.

FIG. 6H again illustrates the user interfaces depicted in FIG. 6G. Whiledevice 600A is continuing to display user interface 634 in FIG. 6H, itshould be recognized that device 600A can display a different userinterface. As described above, user interface 640 on device 600Bincludes first affordance 644A. Referring to FIG. 6H, user input (e.g.,tap input) 607 is received, where user input 607 corresponds toselection of first affordance 644A. In accordance with a determinationthat user input 607 is detected at first affordance 644A, a messaginguser interface is displayed (as depicted in FIG. 6I).

Referring to FIG. 6I, device 600B displays user interface 646 inresponse to selection of first affordance 644A in user interface 640 (asdepicted in FIG. 6H). User interface 646 includes a scrollable list ofaffordances 648, where each affordance is associated with a differentpredefined message. Selection of an affordance in the scrollable list ofaffordance 648 can cause a communication (sometimes referred to as amessage) to be generated with the corresponding predefined message andsent to Molly. For example, selection of second affordance 648B cancause a communication with the text “YOU CAN'T BEAT ME!” to be sent toMolly.

FIG. 6J again illustrates the user interfaces depicted in FIG. 6I. Whiledevice 600A is continuing to display user interface 634 in FIG. 6J, itshould be recognized that device 600A can display a different userinterface. As described above, user interface 646 on device 600Bincludes second affordance 648B. Referring to FIG. 6J, user input (e.g.,tap input) 609 is received, where user input 609 corresponds toselection of second affordance 648B. In accordance with a determinationthat user input 609 is detected at second affordance 648B, acommunication can be generated with text corresponding to secondaffordance 648B and sent to Molly.

Referring to FIG. 6K, device 600B displays user interface 656 inresponse to selection of second affordance 648B in user interface 646(as depicted in FIG. 6J). User interface 656 indicates that a messagehas been sent and includes affordance 658 for causing user interface 656to cease to display.

Also in response to selection of second affordance 648B in userinterface 646 (as depicted in FIG. 6J), device 600A displays userinterface 650 in touch-sensitive display 602A, as depicted in FIG. 6K.User interface 650 includes a representation of the predefined messagesent by Aled, as discussed above. User interface 650 also includes ascrollable list of affordances 652, where each affordance is associatedwith a different operation. For example, the scrollable list ofaffordances 626 includes first affordance 626A for displaying amessaging user interface (as depicted in FIG. 6I) and second affordance626B for ceasing to display user interface 650.

While an activity competition is active, participants in the activitycompetition can receive notifications including a status of the activitycompetition. For example, in response to the activity competitionbeginning, a notification can be displayed to each of the participantsin the activity competition, as depicted in FIG. 6L.

Referring to FIG. 6L, user interface 660 is displayed on touch-sensitivedisplay 602B of device 600B. While not illustrated, a similar userinterface can be displayed on touch-sensitive display 602A of device600A.

User interface 660 indicates that the activity competition with Mollyhas begun. User interface 600 includes a scrollable list of affordances662, where each affordance is associated with a different operation. Forexample, the scrollable list of affordances 626 includes (1) firstaffordance 662A for displaying information related to the activitycompetition, (2) second affordance 662B for displaying a messaging userinterface (as depicted in FIG. 6I), and (3) third affordance 662C forceasing to display user interface 660.

As depicted in FIG. 6L, first affordance 662A includes first portion663A with information related to Aled for the activity competition andsecond portion 663B with information related to Molly for the activitycompetition. The information related to Aled includes icon 663C with anumber indicating a number of times that Aled has won an activitycompetition against Molly. The information related to Aled furtherincludes score 663D for Aled for the activity competition so far. Itshould be recognized that the information included within firstaffordance 662A can be different than illustrated, such as theinformation can include graph 670, as depicted in FIG. 6M and discussedbelow).

Selection of first affordance 662A can cause a user interface withadditional information regarding the activity competition to bedisplayed. For example, the additional information can include graph670, as depicted in FIG. 6M and discussed below.

In addition to a notification being displayed when the activitycompetition begins, notifications can be displayed at predefined timesduring the activity competition. For example, a predefined time can bean absolute time during the activity competition (e.g., each day at 10AM) or as a result of an event occurring on a device where thenotification is displayed (e.g., a participant completing a goal,performing a workout, or accessing a particular application on thedevice). Such notifications can include information related to one ormore active activity competitions.

Referring to FIG. 6M, user interface 664 is displayed on touch-sensitivedisplay 602B in response to a trigger being activated at a predefinedtime. For example, the predefined time can be at 10 PM on Friday,causing user interface 644 to be displayed.

User interface 644 includes a scrollable list of affordances 666, whereeach affordance is associated with a different operation. For example,the scrollable list of affordances 666 includes first affordance 666Afor a first activity competition, second affordance 666B for a secondactivity competition, and third affordance 666C for ceasing to displayuser interface 660. In some examples, the order of affordances foractivity competitions can be based upon when the activity competitionsare finishing. For example, activity competitions finishing sooner canbe included in the scrollable list before activity competitionsfinishing later.

First affordance 666A includes information related to the first activitycompetition. As depicted in FIG. 6M, first affordance 666A includesinformation similar to first affordance 662A (as depicted in FIG. 6L).For example, first affordance 666A (as depicted in FIG. 6M) includesicon 668A with a number indicating a number of times that Molly has wonan activity competition against Aled. First affordance 666A furtherincludes an identification of Molly (e.g., element 668B) and a score forMolly for the first activity competition so far (e.g., element 668C)(sometimes referred to as a cumulative score).

As depicted in FIG. 6M, first affordance 666A further includes graph 670for the first activity competition, where graph 670 includes informationregarding the first activity competition for multiple subsets (e.g.,days). Graph 670 can include more granular information than included inelement 668. The x-axis of graph 670 includes identifications ofmultiple subsets of the first activity competition. As depicted in FIG.6M, each subset is a day of the week (e.g., reference 670A points to “M”for Monday). It should be noted that “M” is located first to indicatethat the first activity competition began on Monday. In addition, itshould be noted that “F” (e.g., reference 670D) is visually highlighted(e.g., circled) in FIG. 6M to indicate that Friday is the current day.

The y-axis of graph 670 includes representations of physical activitydetected for each participant in the first activity competition for eachsubset. For example, representation 670B indicates an amount of physicalactivity detected for Molly (e.g., detected by device 600A andtransmitted to device 600B) on Monday and representation 670C indicatesan amount of physical activity detected for Aled on Monday. By havingrepresentation 670B adjacent to representation 670C, physical activityfor each participant for Monday can easily be compared. It should benoted that representations for Molly are provided to the left ofrepresentations for Aled in graph 670. The configuration is such because600B corresponds to Aled's device. When a subset has not occurred yet(e.g., Saturday as depicted in FIG. 6M), representations correspondingto the subset (e.g., reference 670E) can be displayed as zero.

In some examples, representations for subsets can be normalized acrossthe time period such that the highest representation for a subset of thetime period can be displayed a certain size, with other representationsnormalized based upon the highest representation. For example, if Mollyscored the most points for the time period on Friday, a representationfor Molly on Friday will be the biggest representation. In such anexample, a representation for either Molly or Aled with half the scorewill be represented as half the size of the representation for Molly onFriday.

It should be noted that representations associated with Molly areillustrated as being visually distinct from representations associatedwith Aled in FIG. 6M. For example, icon 668A for Molly is visuallydistinct from the icon for Aled. In addition, representations forsubsets for Molly are visually distinct from representations for subsetsfor Aled.

In some examples, representations associated with a participant that iswinning an activity competition can be highlighted as compared to aparticipant that is losing the activity competition. For example,because Molly's cumulative score is higher than Aled's cumulative score,representations associated with Molly visually appear to be highlightedas compared to representations associated with Aled. Visuallyhighlighting representations associated with a participant that iswinning can allow a participant to quickly assess how they are doing inthe activity competition.

Graph 670 also includes a number of subsets remaining in the firstactivity competition (e.g., reference 670F). For example, as depicted inFIG. 6M, there are two days left in the first activity competition.

Representation 670 also includes icon 670G. Icon 670G can eitherindicate that selection of affordance 666A or icon 670G (depending uponconfiguration of icon 670G) will cause a messaging interface to bedisplayed (as depicted in FIG. 6J).

As depicted in FIG. 6M, second affordance 666B includes informationrelated to the second activity competition between John and Aled. Secondaffordance 666B indicates that John and Aled have competed 11 times,where John has won 4 times and Aled has won 7 times. It should be notedthat second affordance 666B illustrates that different activitycompetitions can begin on different days. For example, the firstactivity competition began on Monday and the second activity competitionbegan on Thursday. It should also be noted that second affordance 666Billustrates that time periods (e.g., 7 days) can be the same acrossdifferent activity competitions.

In addition to a notification being displayed when the activitycompetition begins and at a predefined time, notifications can bedisplayed in response to activity by another participant. For example, anotification can be displayed for Aled in response to physical activityby Molly, such as Molly reaching a goal for a day (such as closing threeactivity rings) or performing a workout. Such notifications can includeinformation related to an activity competition with the otherparticipant.

Referring to FIG. 6N, user interface 672 is displayed on touch-sensitivedisplay 602B in response to Molly reaching her three ring goal for theday. User interface 672 includes a scrollable list of affordances 674,where each affordance is associated with a different operation. Forexample, the scrollable list of affordances 674 includes firstaffordance 674A for an activity competition between Molly and Aled,second affordance 674B for displaying a messaging user interface (asdepicted FIG. 6I), and third affordance 674C for ceasing to display userinterface 672. First affordance 674A is similar to that discussed abovefor first affordance 666A in FIG. 6M.

Notifications can be sent (e.g., displayed on respective devices ofparticipants) to participants of an activity competition when theactivity competition ends. Such notifications can provide results of theactivity competition, including an award of a medal for the winner, andinclude an option to begin a new activity competition, as depicted inFIG. 6O.

Referring to FIG. 6O, user interface 676 is displayed on touch-sensitivedisplay 602A in response to an activity competition between Molly andAled ending. User interface 676 can include text catered to Molly andthe outcome of the activity competition. For example, user interface 676states that “ALED WON.” and includes information that Molly's best daysduring the activity competition were Friday and Monday.

User interface 676 includes a scrollable list of affordances 678, whereeach affordance is associated with a different operation. For example,the scrollable list of affordances 678 includes first affordance 678Afor the activity competition between Molly and Aled, second affordance678B for displaying a messaging user interface (as depicted FIG. 6I),third affordance 678C for initiating a process to start a new activitycompetition (as further discussed below), and fourth affordance 678D forceasing to display user interface 672.

Also in response to the activity competition between Molly and Aledending, user interface 680 is displayed on touch-sensitive display 602B.User interface 680 can include text catered to Aled and the outcome ofthe activity competition. For example, user interface 676 states that“YOU WON.” and includes information that Aled's best day during theactivity competition was Saturday with 794 points.

User interface 680 includes icon 682, representing that Aled won icon682 in response to winning the activity competition. In response towinning icon 682, icon 682 can be placed in a trophy case for Aled, asfurther discussed below for FIG. 8V.

User interface 680 also includes a scrollable list of affordances 684,where each affordance is associated with a different operation. Forexample, the scrollable list of affordances 684 includes firstaffordance 684A for the activity competition between Molly and Aled,second affordance 684B for displaying a messaging user interface (asdepicted FIG. 6I), third affordance 684C for initiating a process tostart a new activity competition (as further discussed below), andfourth affordance 684D for ceasing to display user interface 680.

Having user interface 676 and user interface 680 side-by-side, it shouldbe recognized that representations in a graph (e.g., the graph includedin first affordance 678A and the graph included in first affordance684A) can be swapped depending upon where the graph is being displayed.For example, when the graph is being displayed on Aled's device,representations associated with Aled are generally on the right ofrepresentations associated with Molly. Likewise, when the graph is beingdisplayed on Molly's device, representations associated with Molly aregenerally on the right of representations associated with Alex. Itshould also be noted that FIG. 6O illustrates that highlightedrepresentations have been changed (e.g., swapped) from Molly to Aled(relative to FIG. 6M) because Aled is winning the activity competitiondepicted in FIG. 6O. Such swapping can occur anytime a lead for theactivity competition changes.

FIG. 6P again illustrates the user interfaces depicted in FIG. 6O. Asdescribed above, user interface 676 on device 600A includes thirdaffordance 678C. Referring to FIG. 6P, user input (e.g., tap input) 611is received, where user input 611 corresponds to selection of thirdaffordance 678C. In accordance with a determination that user input 611is detected at third affordance 678C, a user interface related toinitiating an activity competition is displayed (e.g., user interface686 as depicted in FIG. 6Q), an invitation for a new activitycompetition is sent to Aled, and a user interface related to theinvitation is displayed (e.g., user interface 688 as depicted in FIG.6Q). While device 600A is depicted as receiving user input 611, itshould be recognized that device 600B can receive a similar user inputon third affordance 684C, causing similar functionality to be performed.

Referring to FIG. 6Q, user interface 686 is displayed on touch-sensitivedisplay 602A in response to selection of third affordance 678C (asdepicted in FIG. 6P). User interface 686 indicates that an invitationfor an new activity competition has been sent to Aled. User interface686 includes affordance 687 for ceasing to display user interface 686.

Also referring to FIG. 6Q, user interface 688 is displayed ontouch-sensitive display 602B in response to selection of thirdaffordance 678C (as depicted in FIG. 6P). User interface 688 indicatesthat Molly has invited Aled to a new activity competition. Userinterface 688 includes icon 689, representing activity competitionsbetween Molly and Aled. User interface 688 further includes a scrollablelist of affordances 690, where each affordance is associated with adifferent operation. For example, the scrollable list of affordances 690includes first affordance 690A and second affordance 690B.

Similar to as described above for FIG. 6E, selection of first affordance690A accepts the invitation sent by Molly, causing the new activitycompetition between Molly and Aled to begin at a predefined time (e.g.,midnight of the current day) after selection of first affordance 690A.Selection of second affordance 626B can cause device 600B to reject theinvitation (e.g., cause the new activity competition to not begin) andcease to display user interface 688.

FIG. 6R again illustrates the user interfaces depicted in FIG. 6Q. Whiledevice 600A is continuing to display user interface 686 in FIG. 6R, itshould be recognized that device 600A can display a different userinterface. As described above, user interface 688 on device 600Bincludes first affordance 690A. Referring to FIG. 6R, user input (e.g.,tap input) 613 is received, where user input 613 corresponds toselection of first affordance 690A. In accordance with a determinationthat user input 613 is detected at first affordance 690A, a new activitycompetition between Molly and Aled can be set to initiate at apredefined time in the future.

Referring to FIG. 6S, in response to receiving Aled's selection ofaffordance 690A in user interface 688 (as depicted in FIG. 6R), userinterface 694 is displayed on device 600B and user interface 691 isdisplayed on device 600A. User interface 694 indicates that the newactivity competition with Molly will start tomorrow. User interface 694includes icon 695 (which can have the same theme as icon 618, asdepicted in FIG. 6C) and affordance 696, to cease to display userinterface 694.

User interface 691 indicates that the invitation that Molly sent wasaccepted and that the activity competition with Aled will starttomorrow. User interface 691 includes icon 692 (which can have the sametheme as icon 618, as depicted in FIG. 6C). User interface 691 furtherincludes a scrollable list of affordances 693, where each affordance isassociated with a different operation. For example, the scrollable listof affordances 693 includes first affordance 693A for displaying amessaging user interface (as depicted in FIG. 6I) and second affordance693B for ceasing to display user interface 691.

While the figures described above depict an electronic device in theform of a smart watch, it should be recognized that any of the userinterfaces discussed above can be displayed on different electronicdevices, such as a smart phone. In some examples, display of the userinterfaces discussed above on an electronic device with a larger displayarea can include further detail (as depicted in FIG. 6T) not shown onelectronic devices with a smaller display.

Referring to FIG. 6T, user interface 697 is displayed on touch-sensitivedisplay 802 of device 800. In some examples, device 800 includes one ormore features of device 100, 300, 500, or 600. User interface 697includes affordance 698, which includes information related to anactivity competition between Molly and Aled. Similar to as describedabove for FIG. 6M, affordance 698 includes icon 698A with a numberindicating a number of times that Molly has won an activity competitionagainst Aled. Affordance 698 further includes an identification of Molly(e.g., element 698B) and a score for Molly for the activity competitionso far (e.g., element 698C) (sometimes referred to as a cumulativescore).

Also similar to as described above for FIG. 6M, affordance 698 furtherincludes a graph for the activity competition, where the graph includesinformation regarding the activity competition for multiple subsets(e.g., days). The x-axis of the graph includes identifications ofmultiple subsets of the activity competition. As depicted in FIG. 6T,each subset is a day of the week (e.g., reference 698G points to “Mon”for Monday). It should be noted that “Mon” is located first to indicatethat the activity competition began on Monday. In addition, it should benoted that “Fri” (e.g., reference 698J) is visually highlighted (e.g.,circled) in FIG. 6T to indicate that Friday is the current day.

The y-axis of the graph includes representations of physical activitydetected for each participant in the activity competition for eachsubset. For example, representation 698H indicates an amount of physicalactivity received for Molly (e.g., detected by device 600A andtransmitted to device 800) on Monday and representation 698I indicatesan amount of physical activity detected for Aled on Monday. By havingrepresentation 698H adjacent to representation 698I, physical activityfor each participant for Monday can easily be compared. When a subsethas not occurred yet (e.g., Saturday as depicted in FIG. 6T),representations corresponding to the subset (e.g., reference 618K) canbe displayed as zero.

In some examples, representations for subsets can be normalized acrossthe time period such that the highest representation for a subset of thetime period can be displayed a certain size, with other representationsnormalized based upon the highest representation. For example, if Aledscored the most points for the time period on Monday, a representationfor Aled on Monday will be the biggest representation. In such anexample, a representation for either Molly or Aled with half the scorewill be represented as half the size of the representation for Aled onMonday. As depicted in FIG. 6T, the graph further includes value 698Lfor indicating a scale of the graph. The scale can allow a participantto better understand a number of points for each representation in thegraph.

It should be noted that representations associated with Molly areillustrated as being visually distinct from representations associatedwith Aled in FIG. 6T. For example, icon 698A for Molly is visuallydistinct from icon 698D for Aled. In addition, representations forsubsets for Molly are visually distinct from representations for subsetsfor Aled.

In some examples, representations associated with a participant that iswinning an activity competition can be highlighted as compared to aparticipant that is losing the activity competition. For example,because Molly's cumulative score is higher than Aled's cumulative score,representations associated with Molly visually appear to be highlightedas compared to representations associated with Aled. Visuallyhighlighting representations associated with a participant that iswinning can allow a participant to quickly assess how they are doing inthe activity competition.

Unlike graph 670 depicted in FIG. 6M, the graph depicted in FIG. 6Tfurther includes additional information regarding the activitycompetition. For example, the graph includes a daily average number ofpoints for each participant during the activity competition (e.g.,reference 698M and 698N). In particular, the graph states that Molly hasa daily average of 487 points and Aled has a daily average of 442points. In the example depicted in FIG. 6T, the daily average for Mollyis highlighted (e.g., bolded) because Molly is currently winning theactivity competition. It should be recognized that other additionalinformation not included in graph 670 (as depicted in FIG. 6M) can beincluded in the graph depicted in FIG. 6T.

In some examples, points provided to a participant in an activitycompetition are based upon a percentage of a goal reached by theparticipant. For example, a goal can correspond to an amount of walkingfor each day. Such a goal can be set by the participant either beforethe activity begins (in some examples) or at any time during theactivity competition (in other examples). In some examples, differentparticipants in an activity competition can have different goals. Insome examples, points provided to a participant in an activitycompletion are based upon a two-tier scoring system, where scoringchanges when a participant reaches a threshold (e.g., bonus points afterthe threshold).

FIGS. 7A-7B include a flow diagram illustrating a method for displayingan activity competition representation using an electronic device inaccordance with some examples. Method 700 is performed at a device(e.g., 100, 300, 500, 600A, 600B, 800) with a display. Some operationsin method 700 are, optionally, combined, the orders of some operationsare, optionally, changed, and some operations are, optionally, omitted.

As described below, method 700 provides an intuitive way for displayinga user interface on a device corresponding to a first user, where theuser interface includes an activity competition graph (associated withthe first user and a second user) having (1) a score comparison for eachday of an activity competition between the first user and the seconduser and (2) a total sum over the activity competition. The userinterface permits a user viewing the user interface to readily accessphysical activity data corresponding to the second user. The methodreduces the cognitive burden on a user for accessing physical activitydata corresponding to another user, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to access physical activity data corresponding toanother user faster and more efficiently conserves power and increasesthe time between battery charges.

At block 702, the device (e.g., FIG. 6M, 600B, and FIG. 6T, 800)receives first user activity data (e.g., FIG. 6M, data represented bytop right portion of 666A and representations for Aled, and FIG. 6T,data represented by 698D, 698E, 698F, 698I, and other representationsfor Aled) for a time period (e.g., a day, a week, a month) (e.g., FIG.6M, Monday through Sunday for first activity competition and Thursdaythrough Wednesday for second activity competition, and FIG. 6T, Mondaythrough Sunday). The first user activity data includes at least firstuser activity data (e.g., FIG. 6M, data represented by representation670C, and FIG. 6T, data represented by representation 698I) for a firsttime subset (e.g., an hour, a day, a week) (e.g., FIG. 6M, Monday forfirst activity competition and Thursday for second activity competition,and FIG. 6T, Monday) and first user activity data (e.g., FIG. 6M, datarepresented by Aled's representation for Tuesday, and FIG. 6T, datarepresented by Aled's representation for Tuesday) for a second timesubset (e.g., FIG. 6M, Tuesday for first activity competition andWednesday for second activity competition, and FIG. 6T, Tuesday).

In some examples, the first user activity data is received (e.g., viaone or more antennas of the device) by the device (e.g., FIG. 6M, 600B,and FIG. 6T, 800) from a second device (e.g., FIG. 6A, 600A). Forexample, receiving the first user activity data can include detecting,using one or more sensors of the device, the first user activity data.In some examples, the one or more sensors include a heart rate monitor,a GPS locating device, a gyroscope, or the like.

At block 704, the device (e.g., FIG. 6M, 600B, and FIG. 6T, 800)receives second user activity data (e.g., FIG. 6M, data represented bytop left portion of 666A and representations for Molly, and FIG. 6T,data represented by 698A, 698B, 698C, 698H, and other representationsfor Molly) for the time period. The second user activity data includesat least second user activity data (e.g., FIG. 6M, data represented byrepresentation 670B, and FIG. 6T, data represented by representation698H) for the first time subset and second user activity data (e.g.,FIG. 6M, data represented by Molly's representation for Tuesday, andFIG. 6T, data represented by Molly's representation for Tuesday) for thesecond time subset.

In some examples, the second user activity data is received (e.g., viaone or more antennas of the device) by the device from a second device(e.g., FIG. 6A, 600A). For example, receiving the second user activitydata can include receiving the second user activity data from anexternal device (e.g., via a transmission from the external device)(e.g., FIG. 6A, 600A).

In some examples, in response to receiving the second user activity datafrom an external device (e.g., FIG. 6A, 600A), the device (e.g., FIG.6M, 600B, and FIG. 6T, 800) can output an activity notification (e.g.,visual, haptic, or audio alert) (FIG. 6A, 612).

At 712, the device (e.g., FIG. 6M, 600B, and FIG. 6T, 800) displays, onthe display (e.g., FIG. 6M, 602B, and FIG. 6T, 802), a user interface(e.g., FIG. 6M, 664, and FIG. 6T, 697). In some examples, the activitynotification (e.g., FIG. 6M, 612) described above is outputted prior todisplaying the user interface.

In some examples, prior to displaying the user interface (e.g., FIG. 6M,664, and FIG. 6T, 697), the device (e.g., FIG. 6M, 600B, and FIG. 6T,800) displays an activity summary notification (e.g., FIG. 6M, 664 whenthe user interface is FIG. 6N, 672). The activity summary notificationcan include: (1) a first notification element (e.g., informationrelating to an activity competition between the first and second user)(e.g., FIG. 6M, 666A) based on the first user activity data and/or thesecond user activity data; and (2) a second notification element (e.g.,information relating to an activity competition between the third userand the first user) (e.g., FIG. 6M, 666B) based on at least third useractivity data, different from the first user activity data and differentthan the second user activity data.

At 714, the user interface (e.g., FIG. 6M, 664, and FIG. 6T, 697)includes a representation (e.g., graphical or textual indication of avalue) (e.g., FIG. 6M, 670C) of the first user activity data for thefirst time subset.

At 716, the user interface (e.g., FIG. 6M, 664, and FIG. 6T, 697)further includes a representation (e.g., graphical or textual indicationof a value) (e.g., FIG. 6M, Aled's representation for Tuesday) of thefirst user activity data for the second time subset.

At 718, the user interface (e.g., FIG. 6M, 664, and FIG. 6T, 697)further includes a cumulative representation (e.g., a graphical ortextual summary of activity data for the entire time period) (e.g., FIG.6M, top right portion) of the first user activity data for the timeperiod. The cumulative representation of the first user activity datafor the time period is based on at least the first user activity datafor a first time subset and the first user activity data for a secondtime subset. In some examples, the cumulative representation ispresented in the same units as (or different units than) therepresentations of the activity data for the time subsets.

At 720, the user interface (e.g., FIG. 6M, 664, and FIG. 6T, 697)further includes a representation (e.g., FIG. 6M, 670B) of the seconduser activity data for the first time subset. Displaying scores fordifferent users for a day provides feedback as to activity data receivedby the device for the day. Providing improved feedback enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently. The scores also provide an improved man-machine interfaceby reducing the number of interactions to display activity datainformation for multiple users.

In some examples, the representation of the second user activity datafor the first time subset is displayed adjacent to (e.g., next to or ina first region of the user interface) the representation (e.g., FIG. 6M,670C) of the first user activity data for the first time subset. In someexamples, the representation of the first user activity data for thefirst time subset is adjacent (e.g., without any intercedingrepresentations of activity data for other time subsets) to therepresentation of the second user activity data for the first timesubset. Displaying a score for a first user adjacent to a score for asecond user provides comparative feedback to physical activity beingdetected by the device. Providing improved feedback enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

At 722, the user interface (e.g., FIG. 6M, 664, and FIG. 6T, 697)further includes a representation (e.g., FIG. 6M, Molly's representationfor Tuesday) of the second user activity data for the second timesubset. Displaying scores for different days provides feedback as toactivity data received by the device for different days. Providingimproved feedback enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently. The scores also providean improved man-machine interface by reducing the number of interactionsto display activity data information for separate time subsets.

In some examples, the representation of the second user activity datafor the second time subset is displayed adjacent to (e.g., next to or ina second region of the user interface) the representation (e.g., FIG.6M, Aled's representation for Tuesday) of the first user activity datafor the second time subset and is not displayed adjacent torepresentations of second user activity data for any other time subsets.

At 724, the user interface (e.g., FIG. 6M, 664, and FIG. 6T, 697)further includes a cumulative representation (e.g., FIG. 6M, 668A, 668B,and 669C) of the second user activity data for the time period. Thecumulative representation of the second user activity data for the timeperiod can be based on at least the second user activity data for afirst time subset and the second user activity data for a second timesubset. Displaying total scores for users provides feedback as toactivity data being received by the device for the first user and thesecond user. Providing improved feedback enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently. Displaying total scoresfor users provides feedback as to activity data being received by thedevice for the first user and the second user. Providing improvedfeedback enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some examples, the first time subset of the first user activity datacorresponds to the first time subset of the second user activity data.

In some examples, the user interface (e.g., FIG. 6M, 664, and FIG. 6T,697) can further include a representation (e.g., a textualrepresentation; a graphical representation) (e.g., FIG. 6M, 670F) of thenumber of remaining time subsets in the time period.

In some examples, the user interface (e.g., FIG. 6M, 664, and FIG. 6T,697) includes an identification of a current time subset (e.g., FIG. 6M,“F” in first activity competition), where the identification of thecurrent time subset is visually emphasized (e.g., FIG. 6M, circle around“F”).

In some examples, a length of the first time subset is equal to a lengthof the second time subset (e.g., FIG. 6M, Monday through Sunday).

In some examples, displaying the user interface (e.g., FIG. 6M, 664, andFIG. 6T, 697) can further include: (1) in accordance with adetermination that a first value (e.g., FIG. 6M, “2136”) correspondingto the cumulative representation of the first user activity data exceedsa second value (e.g., FIG. 6M, “2303”) corresponding to the cumulativerepresentation of the second user activity data, visually emphasizing(e.g., highlighting) the cumulative representation of the first useractivity data for the time period; and (2) in accordance with adetermination that the second value exceeds the first value, visuallyemphasizing (e.g., FIG. 6M, 668A) the cumulative representation of thesecond user activity data for the time period.

In some examples, the representations can be normalized.

In some examples, the representations can be based upon percentagecompletion of one or more goals. Optionally, the one or more goals areuser defined.

In some examples, the first user activity data corresponds to a firstuser and the second user activity data corresponds to a second user. Insuch examples, prior to displaying the user interface (e.g., FIG. 6M,664, and FIG. 6T, 697), the device displays a competition completionuser interface (e.g., an interface showing details of a previouslycompleted competition) (e.g., FIG. 6P, 680). The competition completionuser interface can include a representation (e.g., FIG. 6P, Aled'sportion of graph) of activity data for the first user for a precedingtime period (e.g., FIG. 6P, Monday through Sunday), a representation(e.g., FIG. 6P, Molly's portion of graph) of activity data for thesecond user for the preceding time period, and a new competitioninitiation affordance (e.g., FIG. 6P, 684C). The competition completionuser interface can also include content (e.g., FIG. 6P, text at top of680) based upon whether the first user or the second user had moreactivity data for the preceding time period. In such examples, thedevice receives a first user input (e.g., FIG. 6P, 611 but on wrongdevice) corresponding to selection of the new competition initiationaffordance and, in response to receiving the first user input, initiatesa process for an activity competition between the first user and thesecond user (e.g., sending an invitation to the second user toaccept/start a competition between the first and second user). In suchexamples, the user interface is displayed after (e.g., in response tothe second user accepting the invitation to start the competition)initiating the process for an activity competition between the firstuser and the second user. Providing different entry points to activitycompetitions provides increased interaction with the device by allowingthe initiation of activity competitions to be available in an intuitivemanner and in multiple locations. Providing entry points as describedherein increases user participation in activity competitions, enhancesthe operability of the device, and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some examples, while displaying the user interface, the devicereceives a second user input corresponding to a request to displayadditional information corresponding to the first user activity dataand/or the second user activity data. In such examples, in response toreceiving the second user input, the device displays a second userinterface including additional information corresponding to the firstuser activity data and/or the second user activity data. In suchexamples, the additional information was not included in the userinterface. In some examples, the additional information includes contactinformation, daily average, actual number of points corresponding toactivity data for particular days, or the like. In some examples, theadditional information functionality occurs when the affordance isincluded in an alert rather than a notification, where an alert must bedismissed before looking at other content using the device and anotification is available for a user to view in the background.

In some examples, while displaying the user interface, the devicereceives a third user input corresponding to a request to display amessaging user interface (e.g., FIG. 6I, 646) for sending a message toan external device (e.g., FIG. 6I, 600A). In such examples, in responseto receiving the third user input, the device displays the messaginguser interface. In some examples, the messaging interface functionalityoccurs when the affordance is included in a notification rather than analert. In some examples, the messaging user interface includes one ormore predefined replies (e.g., FIG. 6I, 648).

In some examples, in response to user input at a location correspondingto a representation, the device displays a messaging user interface(e.g., FIG. 6I, 646). In other examples, in response to user input at alocation corresponding to a representation, the device displaysadditional information regarding a second user corresponding to thesecond user activity data.

In some examples, the first user activity data includes standing data,moving data, and exercise data.

In some examples, the first user activity data corresponds to a firstuser and the second user activity data corresponds to a second user. Insuch examples, the user interface further can include a representation(e.g., FIG. 6M, 668A) based on a comparison of activity data for thefirst user and the second user for one or more previous time periods,preceding the time period.

Note that details of the processes described above with respect tomethod 700 (e.g., FIGS. 7A-7B) are also applicable in an analogousmanner to the methods described below. For example, method 700optionally includes one or more of the characteristics of the variousmethods described below with reference to method 900, method 1100, ormethod 1300. For example, the user interface of method 700 can beincluded in an affordance for an activity competition of method 900. Foranother example, the user interface of method 700 can be based uponactivity data detected based upon the alert of method 1100. For anotherexample, the user interface of method 700 can include pace informationdetected based upon a pace configured as described in method 1300. Forbrevity, these details are not repeated below.

FIGS. 8A-8Y illustrate exemplary user interfaces related to a friendslist for activity sharing in accordance with some examples. The activitysharing can include representations for activity competitions (asdiscussed above in FIGS. 6A-6T and 7A-7B). The friends list can alsoinclude affordances for initiating activity competitions in an intuitivemanner, as further described below.

Referring to FIG. 8A, user interface 804 (referred to as a home screen)is displayed on touch-sensitive display 802 of device 800. Forexplanatory purposes, device 800 belongs to a first user, Aled. Userinterface 804 includes multiple affordances 806 for differentapplications, including affordance 806A for an activity application. InFIG. 8B, device 800 receives selection of affordance 806A and, inresponse, causes a user interface (e.g., user interface 808 as depictedin FIG. 8C) corresponding to the activity application to be displayed.

Referring to FIG. 8C, user interface 808 includes affordance 810D fordisplaying a user interface corresponding to sharing activity data. Asdepicted in FIG. 8C, affordance 810D includes an indication that threenotifications related to the user interface corresponding to sharingactivity data are pending. In FIG. 8D, device 800 receives selection ofaffordance 810D and, in response, causes a user interface (e.g., userinterface 812 as depicted in FIG. 8E) corresponding to sharing activitydata to be displayed.

FIG. 8E illustrates device 800 displaying user interface 812 (sometimesreferred to as a friends list). User interface 812 includes firstportion 814A for information related to activity competitions and secondportion 814B for information related to friends.

As depicted in FIG. 8E, first portion 814A is above second portion 814Bsuch that first portion 814A is displayed before (when scrolling throughthe interface) second portion 814B. Displaying first portion 814A beforesecond portion 814B can affect what is displayed when first portion 814Aand second portion 814B include too much content to be displayed ontouch-sensitive display 802. For example, first portion 814A will bedisplayed in its entirety before any of second portion 814B when firstportion 814A is before second portion 814B in user interface 812. Insuch an example, content not included in touch-sensitive display 802 canbe displayed by in response to a scrolling input.

First portion 812 includes a scrollable list of affordances 816, whereeach affordance is associated with a different activity competition. Forexample, the scrollable list of affordances 816 includes firstaffordance 816A for a first activity competition (between Molly andAled) and second affordance 816B for a second activity competition(between John and Aled). In some examples, the order of affordances foractivity competitions can be based upon when the activity competitionsare finishing. For example, activity competitions finishing sooner canbe included in the scrollable list of affordances 816 before activitycompetitions finishing later.

First affordance 816A includes information related to the first activitycompetition, such as a cumulative score for Molly (i.e., 2303) and Aled(i.e., 2136, labeled “ME”), a number of times Molly has won a pastactivity competition between Molly and Aled (i.e., 23 times), a numberof times Aled has won a past activity competition between Molly and Aled(i.e., 7 times), and an amount of time left in the first activitycompetition (i.e., 2 days left). Second affordance 616B includesinformation related to the second activity competition, which can besimilar to the information related to the first activity competitiondescribed above. It should be noted that, in some examples, affordancesin the scrollable list of affordances 816 can include more or lessinformation than depicted in FIG. 8E, including an affordance includingmore information than another affordance.

Second portion 814B includes a scrollable list of affordances 818, whereeach affordance is associated with a different friend of a user (e.g.,Aled) logged into device 800. For example, the scrollable list ofaffordances 818 includes first affordance 818A for a first friend (i.e.,Jane), second affordance 818B for a second friend (i.e., Molly), andthird affordance 818C for a third friend (i.e., John). It should benoted that, in some examples, friends included in second portion 814Bcan also be included in an activity competition in first portion 814A.For example, Molly is a participant of the first activity competition(e.g., first affordance 816A) and included in the scrollable list ofaffordances 818 (e.g., second affordance 818B). In other examples,friends included in first portion 814A are not included in secondportion 814B.

Each affordance in the scrollable list of affordances 818 includesinformation related to the corresponding friend. For example, firstaffordance 818A corresponds to Jane and includes an identification ofJane (e.g., “Jane”), a percent of goals for Jane that Jane has completed(e.g., “95%), an absolute amount of a goal that Joan has completed withthe absolute amount of the goal (e.g., “400/450”), and icon 818AAvisually depicting an amount of multiple goals that Joan has completed.

User interface 812 further includes sharing affordance 820. Selection ofsharing affordance 820 causes device 800 to display a user interface(e.g., user interface 834 as depicted in FIG. 8O) with sharing details,as further described below with respect to FIG. 8O. Sharing affordance820 includes an indication that three notifications related to sharingdata are pending.

FIG. 8F again illustrates user interface 812 (as depicted in FIG. 8E).As described above, user interface 810 includes first affordance 816A.Referring to FIG. 8F, user input (e.g., tap input) 805 is received bydevice 800, where user input 805 corresponds to selection of firstaffordance 816A in first portion 814A. In accordance with adetermination that user input 805 is detected at first affordance 816Ain the scrollable list of affordances 816, a user interface (e.g., userinterface 822 as depicted in FIG. 8G) with additional informationrelated to the first activity competition (not included in firstaffordance 816A) is displayed.

Referring to FIG. 8G, device 800 displays user interface 822 ontouch-sensitive display 802 in response to selection of first affordance816A in first portion 814A (as depicted in FIG. 8F). User interface 822includes multiple representations 824 of information related to thefirst activity competition. For example, representation 824A is a visualrepresentation of Molly's current completion of activity goals for thecurrent day. The visual representation includes three circles, eachcircle corresponding to a different goal. Representation 824B includesinformation for the first activity competition, as discussed above inFIG. 6T. Representation 824C includes a current status (e.g., 50/500)for Molly completing a first goal (e.g., move goal). Representation 824Dincludes a current status for Molly completing a second goal (e.g.,exercise goal). It should be recognized that user interface 816 caninclude more or fewer representations of information related to thefirst activity competition than depicted in FIG. 8G.

User interface 822 also includes back affordance 826 to cause a previoususer interface (e.g., user interface 812 as depicted in FIG. 8E) to bedisplayed. Referring to FIG. 8H, user input (e.g., tap input) 807 isreceived, where user input 807 corresponds to selection of backaffordance 826. In accordance with a determination that user input 807is detected at back affordance 826, a user interface (e.g., userinterface 812 as depicted in FIG. 8I) is displayed.

FIG. 8I illustrates device 800 displaying user interface 812 in responseto selection of back affordance 826 (as depicted in FIG. 8H). Asdescribed above, user interface 812 includes first affordance 818A insecond portion 814B. Referring to FIG. 8J, user input (e.g., tap input)809 is received, where user input 809 corresponds to selection of firstaffordance 818A. In accordance with a determination that user input 809is detected at first affordance 818A, a user interface (e.g., userinterface 812 as depicted in FIG. 8I) with information related to afriend (e.g., Jane) corresponding to first affordance 818A is displayed.

Referring to FIG. 8K, device 800 displays user interface 828 ontouch-sensitive display 802 in response to selection of first affordance818A in second portion 814B (as depicted in FIG. 8J). User interface 828includes multiple representations 830 of information related to Jane.For example, representation 830A is a visual representation of Jane'scurrent completion of activity goals for the current day. The visualrepresentation includes three circles, each circle corresponding to adifferent goal. Representation 830B includes information related to pastactivity competitions between Jane and Aled. For example, icon 830BAindicates a number (e.g., 7) of past activity competitions that Janebeat Aled (e.g., “ME”) and icon 830BB indicates a number (e.g., 2) ofpast activity competitions that Aled beat Jane. Representation 830Cincludes a current status (e.g., 400/500) for Jane completing a firstgoal (e.g., move goal).

User interface 828 also includes invite affordance 831 to initiate aprocess for beginning an activity competition between Jane and Aled. Forexplanatory purposes, selection of invite affordance 831 can cause userinterface 616 (as depicted in FIG. 6C) or user interface 686 (asdepicted in FIG. 6Q) to be displayed on touch-sensitive display 802.

Referring to FIG. 8K, user interface 828 also includes back affordance832 to cause a previous user interface (e.g., user interface 812 asdepicted in FIG. 8J) to be displayed. Referring to FIG. 8L, user input(e.g., tap input) 811 is received, where user input 811 corresponds toselection of back affordance 832. In accordance with a determinationthat user input 811 is detected at back affordance 832, a user interface(e.g., user interface 812 as depicted in FIG. 8M) is displayed.

FIG. 8M illustrates device 800 displaying user interface 812 in responseto selection of back affordance 832 (as depicted in FIG. 8L). Asdescribed above, user interface 812 includes sharing affordance 820.Referring to FIG. 8N, user input (e.g., tap input) 813 is received,where user input 813 corresponds to selection of sharing affordance 820.In accordance with a determination that user input 813 is detected atsharing affordance 820, a user interface (e.g., user interface 834 asdepicted in FIG. 8O) is displayed.

Referring to FIG. 8O, device 800 displays user interface 834 ontouch-sensitive display 802 in response to selection of sharingaffordance 820 (as depicted in FIG. 8N). User interface 834 is dividedinto multiple portions (e.g., first portion 836 and second portion 838),each portion including a different type of information.

First portion 836 includes information related to invitations foractivity competitions received by device 800. For example, first portion836 includes invitation 836A. Invitation 836A indicates that Tom hassent an invitation to begin an activity competition to Aled (e.g., toone or more devices (e.g., device 800) associated with Aled). Invitation836A includes an accept affordance and an ignore affordance in order torespond to the invitation from Tom. Selection of the accept affordanceinitiates a process to begin an activity competition between Tom andAled. Selection of the ignore affordance removes invitation 836A fromfirst portion 836.

Second portion 838 includes information related to invitations foractivity competitions sent by device 800. For example, second portion838 includes invitation 838A. Invitation 838A indicates that Aled hassent an invitation to begin an activity competition to Jane. Invitation838A includes a representation of the amount of time that remains forJane to accept the invitation.

FIG. 8P illustrates device 600B (e.g., a second device associated withthe same user, Aled) displaying user interface 840 on touch-sensitivedisplay 602B. User interface 840, like user interface 812 (as depictedin FIG. 8E), corresponds to a friends list. However, unlike userinterface 812, user interface 840 is configured to be used on anelectronic device with a smaller display area than device 800.

Similar to user interface 812, user interface 830 includes first portion842A and second portion 842B. As depicted in FIG. 8P, first portion 842Ais above second portion 842B such that first portion 842A is displayedbefore second portion 842B. Displaying first portion 842A before secondportion 842B can affect what is displayed when first portion 842A andsecond portion 842B include too much content to be displayed ontouch-sensitive display 602B. For example, first portion 842A will bedisplayed in its entirety before any of second portion 842B when firstportion 842A is before second portion 842B in user interface 812. Insuch an example, content not included in touch-sensitive display 802 canbe displayed by in response to a scrolling input (e.g., rotation ofrotatable input mechanism 604A).

Referring to FIG. 8P, first portion 842A includes a scrollable list ofaffordances 844, where each affordance is associated with a differentactivity competition. For example, the scrollable list of affordances844 includes first affordance 844A for a first activity competition(between Molly and Aled) and second affordance 816B for a secondactivity competition (between John and Aled). In some examples, theorder of affordances for activity competitions can be based upon whenthe activity competitions are finishing. For example, activitycompetitions finishing sooner can be included in the scrollable list ofaffordances 844 before activity competitions finishing later.

First affordance 844A includes information related to the first activitycompetition, such as a cumulative score for Molly (i.e., 2303) and Aled(i.e., 2136), a number of times Molly has won a past activitycompetition between Molly and Aled (i.e., 23 times), a number of timesAled has won a past activity competition between Molly and Aled (i.e., 7times), and an amount of time left in the first activity competition(i.e., 2 days left). Second affordance 616B includes information relatedto the second activity competition, which can be similar to theinformation related to the first activity competition described above.It should be noted that, in some examples, affordances in the scrollablelist of affordances 816 can include more or less information thandepicted in FIG. 8E, including an affordance including more informationthan another affordance.

It should also be noted that while user interface 840 is depicted ashaving the same information in first portion 842A as user interface 812in first portion 814A, an organization of the information in userinterface 840 is different than an organization of the information inuser interface 812. The difference in organization can be because oftouch-sensitive display 602B having a smaller display area thantouch-sensitive display 802.

Second portion 842B includes a scrollable list of affordances 846, whereeach affordance is associated with a different friend of a user (e.g.,Aled) logged into device 800. For example, the scrollable list ofaffordances 846 includes first affordance 846A for a first friend (i.e.,Jane), second affordance 846B for a second friend (i.e., Molly), thirdaffordance 846C for a third friend (i.e., John), and fourth affordance846D for a fourth friend (i.e., Tom). It should be noted that, in someexamples, friends included in second portion 842B can also be includedin an activity competition in first portion 842A. For example, Molly isa participant of the first activity competition (e.g., first affordance842A) and included in the scrollable list of affordances 846 (e.g.,second affordance 846B). In other examples, friends included in firstportion 842A are not included in second portion 842B.

Each affordance in the scrollable list of affordances 846 includesinformation related to the corresponding friend. For example, firstaffordance 846A corresponds to Jane and includes an identification ofJane (e.g., “Jane”), a percent of goals for Jane that Jane has completed(e.g., “95%), an absolute amount of a goal that Joan has completed withthe absolute amount of the goal (e.g., “400/450”), and an icon visuallydepicting an amount of multiple goals that Joan has completed.

FIG. 8P depicts some information related to a friend not illustrated inFIG. 8E. Such information can also be included in FIG. 8E. For example,second affordance 846B in second portion 842B includes icon 846BA. Icon846BA indicates that Aled has won an activity competition between Aledand Molly. Icon 846BA can be a unique identification of activitycompetitions between Aled and Molly such that other icons for otheractivity competitions between other participants have a different theme(as depicted for icon 846CA).

FIG. 8P also depicts invitation icon 842 included in third affordance846D in second portion 842B. Invitation icon 842 indicates that a friendcorresponding to third affordance 846D (e.g., Tom) has sent aninvitation to compete in an activity competition with Aled. Invitationicon 842 also includes a number indicating how many invitations from Tomhave been received.

FIG. 8Q again illustrates user interface 840 (as depicted in FIG. 8P).As described above, user interface 810 includes fourth affordance 846Dwith invitation icon 842. Referring to FIG. 8Q, user input (e.g., tapinput) 815 is received, where user input 815 corresponds to selection ofinvitation icon 842 or fourth affordance 846D (depending upon how userinterface 840 is configured). In accordance with a determination thatuser input 815 is detected at invitation icon 842 (or fourth affordance846D), a user interface (e.g., user interface 848 as depicted in FIG.8R) is displayed.

Referring to FIG. 8R, device 800 is displaying user interface 848 inresponse to selection of invitation icon 842 (or fourth affordance 846D)(as depicted in FIG. 8Q). User interface 848 indicates that Tom hasinvited Aled to a 7 day activity competition. User interface 848includes activity data for Tom for a current day. User interface 848further includes a scrollable list of affordances 850, where eachaffordance is associated with a different operation. For example, thescrollable list of affordances 850 includes first affordance 850A andsecond affordance 850B.

Selection of first affordance 850A can accept the invitation for theactivity competition sent by Tom. Acceptance of the invitation can causethe activity competition to begin at a predefined time after theselection (e.g., midnight of the current day), as further describedbelow. Selection of second affordance 850B can cause device 600B toreject the invitation (e.g., cause the activity competition to notbegin) and cease to display user interface 848. Selection of secondaffordance 850B can further cause invitation icon 842 to be removed fromfourth affordance 846D.

FIG. 8S again illustrates user interface 848 (as depicted in FIG. 8R).As described above, user interface 810 includes first affordance 850A.Referring to FIG. 8S, user input (e.g., tap input) 817 is received,where user input 817 corresponds to selection of first affordance 850A.In accordance with a determination that user input 817 is detected atfirst affordance 850A, a user interface (e.g., user interface 852 asdepicted in FIG. 8T) is displayed.

Referring to FIG. 8T, device 600B displays user interface 852 inresponse to selection of first affordance 850A in user interface 848 (asdepicted in FIG. 8S). User interface 852 indicates that an activitycompetition between Tom and Aled starts tomorrow. User interface 852includes icon 854, which represents activity competitions between Tomand Aled. User interface also includes affordance 856. Selection ofaffordance 856 causes device 600B to cease to display user interface852.

FIG. 8U again illustrates user interface 808 (as depicted in FIG. 8C).User interface 810 includes third affordance 810C. In response toselection of third affordance 810C (as depicted in FIG. 8V), device 800displays user interface 858 (as depicted in FIG. 8W).

Referring to FIG. 8W, user interface 858 (sometimes referred to as atrophy case) relates to awards that have been given to Aled. Userinterface 858 is divided into multiple portions 860, where each portionincludes a different type of award. For example, portions 860 includesrecents 860A, competitions 860B, monthly challenges 860C, achievements860D, and workouts 860E.

Each portion can include one or more awards associated with acorresponding type of award. For example, recents 860 can include awardsthat have been awarded within a particular amount of time from a currenttime. In some examples, awards in recents 860 can be larger than awardsin other portions. Competitions 860B can include awards that have beenawarded for activity competitions. Monthly challenges 860C can includeawards that have been predefined as a monthly challenge. Achievements860D can include awards that have been predefined as an achievement.Workouts 860E can include awards that have been awarded using a workoutapplication (as described herein).

In some examples, some awards in a portion might not be visible. In suchexamples, the awards can be navigated by side scrolling through them.

Display of awards in user interface 858 can differ based upon theparticular award. For example, a representation for an award that isreceived only once on a particular day can include an icon (e.g., icon862A), an identification of the award (e.g., identification 862B), and adate that the award was received (e.g., date 862C). In some examples, arepresentation for an award that is received only once on a particularday can include an icon (e.g., icon 862A), an identification of theaward (e.g., identification 862B), and further information related toachieving the award, such as a number of calories burned which satisfiedat least a minimum amount for the award (e.g., calories 872C). In suchexamples, the representation might not include a date that the award wasreceived because the identification indicates the date.

For another example, a representation for an award that is receivedmultiple times can include an icon (e.g., icon 864A or 866A), anidentification of the award (e.g., identification 864B or 866B), and anumber of times that the award has been received (e.g., number 864D or866C). In some examples, the representation for an award that isreceived multiple times can also include a date that the award has lastbeen received (e.g., date 864C). In such examples, the representationcan also include the date when the award is predefined as hard toreceive or the award has been received below a particular number oftimes.

It should be noted that each icon for each award in competitions 860B(e.g., icons 866A, 868A, and 870A) is different. This can be due to eachactivity competition being assigned a different representation, asdiscussed herein.

FIG. 8X again illustrates user interface 858 (as depicted in FIG. 8W).User interface 810 includes icon 866A of representation 866. In responseto selection of icon 866A (or representation 866) (as depicted in FIG.8X), device 800 displays user interface 876 (as depicted in FIG. 8X).Referring to FIG. 8X, user interface 876 includes icon 878A (whichcorresponds to icon 866A (as depicted in FIG. 8W), identification 873Bof an award corresponding to icon 878 (which corresponds toidentification 866B), and further information not included inrepresentation 866 (as depicted in FIG. 8W). The further informationincludes a description of the award (reference 878C) and a date that theaward was last received (reference 878D).

FIGS. 9A-9B include a flow diagram illustrating a method for displayinga friends list representation using an electronic device in accordancewith some examples. Method 900 is performed at a device (e.g., 100, 300,500, 600A, 600B, 800) with a display. Some operations in method 900 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

As described below, method 900 provides an intuitive way for displayinga user interface on a device corresponding to a first user, where theuser interface includes affordances for multiple activity competitions,where each activity competition (1) is between the first user andanother user and (2) is represented by current scores for the activitycompetition and a number of days remaining in the activity competition.The user interface permits a user viewing the user interface to readilyaccess physical activity data corresponding to multiple users. Themethod reduces the cognitive burden on a user for accessing physicalactivity data corresponding to multiple user, thereby creating a moreefficient human-machine interface. For battery-operated computingdevices, enabling a user to access physical activity data correspondingto multiple users faster and more efficiently conserves power andincreases the time between battery charges.

At 902, the device (e.g., FIG. 8A, 800) receives first user activitydata (e.g., FIG. 8C, data represented in FIG. 8C) for a first user(e.g., Aled), where the first user activity data corresponds to a firsttime period (e.g., a day, a week, a month, a duration of an activitycompetition between the first user and a second user) (e.g., FIG. 8I,Monday through Sunday for activity competition with Molly) and a secondtime period (e.g., a day, a week, a month, a duration of an activitycompetition between the first user and a user; a time period differentthan the first time period) (e.g., FIG. 8I, Thursday through Wednesdayfor activity competition with John). In some examples, the first useractivity data is received via one or more sensors of the device.

In some examples, a length (e.g., FIG. 8I, 7 days for activitycompetition with Molly) of the first time period is the same as a length(e.g., FIG. 8I, 7 days for activity competition with John) of the secondtime period. In some examples, a length of the first time period isdifferent from a length of the second time period. In some examples, thefirst time period and the second time period overlap (e.g., FIG. 8I,activity competition with Molly and activity competition with John).

At 904, the device (e.g., FIG. 8A, 800) receives second user activitydata (e.g., FIG. 8H, data represented by representations for Molly) fora second user (e.g., FIG. 8I, Molly), where the second user activitydata corresponds to the first time period, and where the first timeperiod includes a first elapsed (e.g., completed) sub-period (e.g., FIG.8H, Monday through Friday) and a first unelapsed (e.g., remaining)sub-period (e.g., FIG. 8H, Saturday through Sunday) for an activitycompetition (e.g., FIG. 8H) between the first user and the second user.In some examples, the second user activity data is received (e.g., viaone or more antennas of the device) by the device from a second device(e.g., a device associated with Molly).

At 906, the device (e.g., FIG. 8A, 800) receives third user activitydata (e.g., FIG. 8I, data represented by representations for John) forthe third user (e.g., FIG. 8I, John), where the third user activity datacorresponds to the second time period, and where the second time periodincludes a second elapsed sub-period (e.g., FIG. 8I, Thursday throughFriday) and a second unelapsed sub-period (e.g., FIG. 8I, Saturdaythrough Wednesday) for an activity competition (e.g., FIG. 8I, activitycompetition with John) between the first user and the third user. Insome examples, the third user activity data is received (e.g., via oneor more antennas of the device) by the device from a third electronicdevice (e.g., a device associated with John).

In some examples, the activity competition between the first user andthe second user began at a first time (e.g., FIG. 8I, Monday), and wherethe activity competition between the first user and the third user beganat a second time (e.g., FIG. 8I, Thursday) different from the firsttime.

At 908, the device (e.g., FIG. 8A, 800) displays, on the display (e.g.,FIG. 8A, 802), a user interface (e.g., FIG. 8E, 812). In some examples,the user interface is for a friends list.

At 910, the user interface (e.g., FIG. 8E, 812) includes arepresentation (e.g., FIG. 8E, 816A) of the first user activity data andthe second user activity data during the first elapsed sub-period forthe activity competition between the first user and the second user. Insome examples, the representation of the first activity data and thesecond activity data is a score for each of the first user and thesecond user.

At 912, the user interface (e.g., FIG. 8E, 812) includes an indicationof an amount of time in the first unelapsed sub-period (e.g., FIG. 8E,816A with “2 days left”) for the activity competition between the firstuser and the second user. In some examples, the indication is aremaining amount of time in the activity competition.

At 914, the user interface (e.g., FIG. 8E, 812) includes arepresentation (e.g., FIG. 8E, 816B) of the first activity data and thethird activity data during the second elapsed sub-period for theactivity competition between the first user and the third user. In someexamples, the representation of the first activity data and the thirdactivity data is a score for each of the first user and the third user.Displaying information for multiple activity competitions providesfeedback as to activity data being received by the device for multipledifferent users. Providing improved feedback enhances the operability ofthe device and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently. The information formultiple activity competitions also provides an improved man-machineinterface by reducing number of interactions to display information fordifferent activity competitions.

At 916, the user interface (e.g., FIG. 8E, 812) includes an indicationof an amount of time in the second unelapsed sub-period (e.g., FIG. 8E,816B with “5 days left”) for the activity competition between the firstuser and the third user. Displaying remaining time in activitycompetitions provides feedback as to activity data to be received in thefuture. Providing improved feedback enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently. The remaining time alsoprovides an improved man-machine interface by increasing an amount ofsustained interaction with the device based upon an amount of theremaining time.

In some examples, the user interface (e.g., FIG. 8E, 812) furthercomprises: (1) a first portion (e.g., FIG. 8E, 814A) including therepresentations and the indications; and (2) a second portion (e.g.,FIG. 8E, 814B) visually distinct from the first portion, the secondportion including: (1) a first affordance (e.g., FIG. 8E, 818A) with anidentification (e.g., FIG. 8E, “Jane) of the second user; (2) a secondaffordance (e.g., FIG. 8E, 818B) with an identification (e.g., FIG. 8E,“Molly”) of the third user; and (3) a third affordance (e.g., FIG. 8E,818C) with an identification (e.g., FIG. 8E, “John”) of a fourth usernot in an active activity competition with the first user. Displayingcompeting friends different than non-competing friends provides feedbackas to data received by the device (e.g., where the data is coming from).Providing improved feedback enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently. Displaying a first setof friends differently from a second set of friends also provides animproved man-machine interface by emphasizing one set of friends overanother.

In some examples, the third affordance includes a notification (e.g.,FIG. 8P, 842) that the fourth user has requested to initiate an activitycompetition between the first user and the fourth user. In suchexamples, the device receives a first user input (e.g., FIG. 8Q, 815)corresponding to selection of the third affordance. In response toreceiving the first user input, the device initiates a process forstarting an activity competition between the first user and the fourthuser, where the activity competition between the first user and thefourth user causes first user activity data and fourth user activitydata to be received during a time period (e.g., 7 days starting fromwhen the activity competition between Tom and Aled begins). Displayingan additional entry point for an activity competition next to a friend'sname in a friends list provides feedback as to pending requests fromuser's in an intuitive location. Providing improved feedback enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some examples, the notification is removed from the third affordanceafter an amount of time (e.g., 48 hours) has passed since the fourthuser sent a corresponding request to initiate the activity competitionbetween the first user and the fourth user.

In some examples, while displaying the user interface (e.g., FIG. 8E,812), the device (e.g., FIG. 8A, 800) receives a second user input(e.g., an input corresponding to the representation of the first useractivity data and the second user activity data) (e.g., FIG. 8F, 805)corresponding to a request to display additional information regardingthe activity competition between the first user and the second user. Inresponse to receiving the second user input, the device displays asecond user interface (e.g., FIG. 8G, 822) including the additionalinformation. In some examples, the additional information includes (1) arepresentation (e.g., FIG. 8E, “Me”) of the first user activity dataduring a portion of the first elapsed sub-period for the activitycompetition between the first user and the second user and (2) arepresentation (e.g., FIG. 8G, 824B) of the second user activity dataduring the portion of the first elapsed sub-period for the activitycompetition between the first user and the second user.

In some examples, the representation of the first user activity data andthe second user activity data includes: an identification of the firstuser (e.g., FIG. 8E, “Me”); an identification of the second user (e.g.,FIG. 8E, “Molly”); and a representation based on a comparison ofactivity data for the first user and the second user for one or moreprevious time periods, preceding the time period (e.g., FIG. 8E, “23” in816A)

In some examples, the third affordance (e.g., FIG. 8P, 846C) includes afirst icon (e.g., a graphical element) (e.g., FIG. 8P, 846CA) indicatingprevious (e.g., assigned to) activity competitions between the firstuser and the fourth user.

In some examples, selection of the fourth affordance (e.g., FIG. 8J,809) causes a user interface (e.g., FIG. 8K, 828) to be displayed with arepresentation (e.g., FIG. 8K, 830BA) indicating previous activitycompetitions between the first user and the fourth user.

In some examples, the second affordance includes a second iconindicating previous activity competitions between the first user and thethird user, where the first icon has a first visual theme (e.g., ashape, a background color or pattern, and where the second icon with asecond visual theme different from the first visual theme. In someexamples, two graphical indications may share a common visual theme,while differing in non-thematic visual elements (e.g., such as a numberor initials that are not part of the visual theme. In some examples,unique visual themes are assigned to each other user (e.g., a seconduser, a third user) that has been, or is currently, in a competitionwith the user of the electronic device (e.g., the first user.

In some examples, icons for different activity competitions between thesame two participants are the same.

In some examples, while displaying the user interface, receiving a thirduser input (e.g., FIG. 8V, 819) corresponding to a request to display anawards user interface (e.g., FIG. 8W, 858); in response to receiving thethird user input, the device displays, on the display, a third userinterface (e.g., FIG. 8W, 858) including: a first portion (e.g., FIG.8W, 860B) corresponding to a first type of icons, where the first typeof icons relates to activity competitions, where the first portionincludes the first icon (e.g., FIG. 8W, 866A) and the second icon (e.g.,FIG. 8W, 868A); and a second portion (e.g., FIG. 8W, 860E) correspondingto a second type of icons, where the second portion includes a thirdicon (e.g., FIG. 8W, star icon). In some examples, the third userinterface is a trophy case. In some examples, the first portion includesicons related to activity competitions. In some examples, the secondportion includes icons related to workouts. In some examples, the thirduser interface further includes a third portion (e.g., FIG. 8W, 860A)corresponding to icons recently received, where icons included in thethird portion are visually distinct (e.g., bigger) than icons in otherportions. In some examples, icons in a portion are configured to be sidescrolled.

In some examples, the third user interface, for an icon (e.g., FIG. 8W,864) included in the third user interface, includes one or more of thefollowing adjacent to the icon: an identification of the icon (e.g.,FIG. 8W, 864B) and a number of times the icon has been earned (e.g.,FIG. 8W, 864D).

In some examples, the device receives a fourth user input (e.g., FIG.8Q, 815) corresponding to selection of the third affordance. In responseto receiving the fourth user input, the device displays a third userinterface (e.g., FIG. 8R, 848) comprising a competition initiationaffordance (e.g., FIG. 8R, 850A). The device receives a fifth user input(e.g., FIG. 8S, 817) corresponding to the competition initiationaffordance. In response to receiving the fifth user input, the deviceinitiates an activity competition between the first user and the fourthuser, where the activity competition between the first user and thefourth user causes first user activity data and fourth user activitydata to be received during a third time period.

In some examples, the representation of the first user activity data andthe second user activity data during the first elapsed sub-period forthe activity competition between the first user and the second user isbased upon a two-tier scoring system, where scoring changes when a userreaches a threshold (e.g., bonus points).

In some examples, while displaying the user interface, the devicereceives, using a rotatable input mechanism (e.g., an input mechanismthat can rotate relative to a housing of the device) (e.g., FIG. 8P,604A) of the device, a sixth user input. In response to receiving thesixth user input, the device updates the user interface to display afourth affordance for a fifth user, where the fourth affordance is notvisible prior to receiving the sixth user input.

Note that details of the processes described above with respect tomethod 900 (e.g., FIGS. 9A-9B) are also applicable in an analogousmanner to the methods described below/above. For example, method 900optionally includes one or more of the characteristics of the variousmethods described below with reference to method 700, method 1100, ormethod 1300. For example, the user interface of method 900 can lead to(e.g., by selecting an affordance in first portion) to the userinterface of method 700. For another example, the user interface ofmethod 1100 can generate activity data that is represented in the userinterface of method 900. For another example, the user interface ofmethod 1300 can generate activity data that is represented in the userinterface of method 900. For brevity, these details are not repeatedbelow.

FIGS. 10A-10Q illustrate exemplary user interfaces associated withalerts presented to a user in response to automatically determining aboundary of a workout in accordance with some examples. For example,FIG. 10A depicts an alert presented in response to automaticallydetermining a beginning of a workout and FIG. 10D depicts an alertpresented in response to automatically determining an end of a workout.Such alerts reduce the need for a user to remember to start and/or end aworkout. The user interfaces in these figures are used to illustrate theprocesses described below, including the processes in FIG. 11.

Referring to FIG. 10A, user interface 1004 of a workout application isdisplayed on touch-sensitive display 602A of device 600A. In someexamples, user interface 1004 is displayed in response to adetermination that a user wearing device 600A has begun an outdoor run.The determination can be based upon data detected by one or more sensorsassociated with device 600A. For example, device 600A can include or bepaired with a heart-rate monitor and a GPS sensor. In response toheart-rate information detected by the heart-rate monitor and GPSinformation detected by the GPS sensor, device 600A (or a deviceconnected to device 600A) can determine that the user is likely runningoutside.

User interface 1004 includes a scrollable list of affordances 1006,where each affordance is associated with a different operation. Forexample, the scrollable list of affordances 1006 includes startaffordance 1006A, change affordance 1006B, and dismiss affordance 1006C.Start affordance 1006A causes a physical activity tracking functionconfigured for outdoor runs to be launched. Change affordance 1006Ballows a user to pick a different type of workout such that a physicaltracking function configured for the different type of workout islaunched. Dismiss affordance 1006C causes user interface 1004 to ceaseto display.

User interface 1004 further includes physical activity icon 1008corresponding to the outdoor run. Physical activity icon 1008 is an iconof a runner. In various examples, physical activity icon 1008 isdisplayed in an animated state, as further illustrated in FIG. 10I.

In some examples, content included in user interface 1004 might not fitwithin touch-sensitive display 602A; in which case content not displayedcan be displayed in response to a scrolling input (e.g., rotation ofrotatable input mechanism 604A).

In some examples, an alert (e.g., user interface 1004) is reissued(e.g., re-displayed or a new alert corresponding to the alert isdisplayed) after an amount of time (e.g., a predetermined amount oftime) has passed without causing the alert to be dismissed (e.g.,selecting an affordance in the scrollable list of affordances 1006). Forexample, if a user does not select an affordance in the scrollable listof affordances 1006 within 3 minutes, a new user interface that is thesame or similar to user interface 1004 is displayed on touch-sensitivedisplay 602A of device 600A. In some examples, if the user does selectan affordance (e.g., dismiss affordance 1006A) within three minutes ofuser interface 1004 being displayed, user interface 1004 is not reissuedafter 3 minutes. While 3 minutes is used as an example, it should berecognized that a different amount of time may be used.

In some examples, the alert is only reissued when the alert has beeninterrupted (e.g., user interface 1004 is no longer being displayed dueto another alert). In some examples, if the alert has not beeninterrupted, the alert remains (e.g., continues to be displayed and/oris displayed whenever touch-sensitive display 602A transitions from aninactive state to an active state) for a particular amount of time. Insome examples, the particular amount of time is based on a type ofworkout corresponding to the alert. For example, if the alertcorresponds to swimming, the alert can remain for 60 minutes; and if thealert corresponds to running or some other type of workout other thanswimming, the alert can remain for 30 minutes. In some examples, anotification corresponding to user interface 1004 can be sent to anotification center such that a user is able to view the notificationafter user interface 1004 ceases to display.

In some examples, prior to displaying user interface 1004, userinterface 1064 is displayed on touch-sensitive display 602A of device600A, as depicted in FIG. 10L. In such examples: user interface 1064 isdisplayed in response to the determination that a user wearing device600A has begun an outdoor run, and user interface 1004 is displayedafter displaying user interface 1064 (e.g., in response to userinterface 1004 being displayed for a particular amount of time). In someexamples, when user interface 1064 is displayed, user interface 1004 isdisplayed in response to a determination that a set of one or moreshort-look criteria has been met and user interface 1064 is displayed inresponse to a determination that a set of one or more long-look criteriahas been met, as discussed below.

As depicted in FIG. 10L, user interface 1064 includes physical activityicon 1066 corresponding to the outdoor run. In various examples,physical activity icon 1064 is displayed in an animated state, asfurther illustrated in FIG. 10I. In some examples, content such asphysical activity icon 1064 is included in both user interface 1064 anduser interface 1004 (where it is referred to as physical activity icon1008). In such examples, user interface 1004 includes additional contentthat is not included in user interface 1064, such as the scrollable listof affordances 1006. User interface 1064 further includes text toindicate that user interface 1064 is being displayed because it has beendetermined that the user is running (e.g., “Looks like you're running”).

In some examples, user interface 1064 is displayed in response todetecting a user input within a first time interval following aperceptual output (e.g., thereby satisfying short-look criteria).Information in user interface 1064 may be referred to as first portionof information. In such examples, after raising a user's wrist to viewuser interface 1064, the user may then wish to view more informationassociated with user interface 1064. If device 600A determines that theuser continues to maintain device 600A in a viewing position for apredetermined time interval (e.g., thereby satisfying a long-lookcriteria) after displaying user interface 1064, device 600A displaysuser interface 1004, which may be referred to as a second portion of theinformation. That is, in some examples, device 600A can automaticallytransition from displaying user interface 1064 to displaying userinterface 1004 when the user holds device 600A in a viewing position andwaits.

FIG. 10B again illustrates user interface 1004 (as depicted in FIG.10A). As described above, user interface 1004 includes start affordance1006A. Referring to FIG. 10B, user input (e.g., tap input) 1001 isreceived, where user input 1001 corresponds to selection of startaffordance 1006A. In accordance with a determination that user input1001 is detected at start affordance 1006A in the scrollable list ofaffordances 1006, a physical activity tracking function configured foroutdoor runs is launched.

In response to selection of start affordance 1006A, user interface 1026(which is depicted in FIG. 10C) is displayed. User interface 1026displays (e.g., provide feedback regarding) data detected by device 600Afor the outdoor run. In some examples, the displayed data can be basedupon data detected prior to selection of start affordance 1006A and/orprior to display of user interface 1004. For example, a preliminarydetermination that the user is performing the outdoor run can be made.At some time after the preliminary determination, a final determinationthat the user is performing the outdoor run can be made, the finaldetermination causing user interface 1004 to be displayed. In such anexample, all data since the preliminary determination can be used whencalculating data to display in user interface 1026. For another example,in response to selection of start affordance 1006A, an amount of dataprior to the selection can be determined to likely (e.g., above athreshold) be associated with the outdoor run, where the amount of datais used when calculating data to display in user interface 1026.

To display the data detected by device 600A, user interface 1026includes representations 1028. In FIG. 10C, representations 1028 includetotal mileage 1028A (e.g., an indication of a number of miles traveledduring the outdoor run), average pace per mile 1028B (e.g., anindication of an average amount of time it has taken for device 600A totravel a mile during the outdoor run), total time 1028C (e.g., anindication of a duration of the outdoor run), and total calories 1028D(e.g., an indication of an amount of calories determined to be burned bythe user during the outdoor run). It should be recognized that, in someexamples, user interface 1026 can include more or fewer representations.

User interface 1026 also includes a current time, a physical activityicon (as discussed above), or other information determinable by device600A. The physical activity icon depicted in user interface 1026 can beanimated. While FIG. 10C depicts a particular visual appearance ofrepresentations 1028, it should be recognized that representations 1028can appear differently.

At some point after a workout has started (e.g., after selection ofstart affordance 1006A), it can be determined that the user is likely(e.g., above a threshold criteria) no longer running outside. Thedetermination can be based upon similar data as described above forbeginning the outdoor run, such as data detected by one or more sensorsassociated with device 600A. In response to the determination that theuser is likely no longer running outside, user interface 1038 (asdepicted in FIG. 10D) is displayed on touch-sensitive display 602A.

User interface 1038 includes a scrollable list of affordances 1040,which are associated with different operations. For example, thescrollable list of affordances 1040 includes end affordance 1040A, pauseaffordance 1040B, change affordance 1040C, and dismiss affordance 1006D.End affordance 1040A causes the physical activity tracking functioncorresponding to the outdoor run to stop and data generated by thephysical tracking function to be stored as a previous workout. Pauseaffordance 1040B causes the physical activity tracking functioncorresponding to the outdoor run to pause. Change affordance 1040Callows a user to choose a different type of workout so that a differentphysical activity tracking function corresponding to the different typeof workout can be launched. Dismiss affordance 1006D causes userinterface 1038 to cease to display and the physical activity trackingfunction for the outdoor run to continue to execute.

User interface 1038 further includes physical activity icon 1042corresponding to the outdoor run. Physical activity icon 1042 is an iconof a runner. In various examples, physical activity icon 1042 isdisplayed in a static state.

In some examples, content included in user interface 1038 might not fitwithin touch-sensitive display 602A; in which case content not displayedcan be displayed in response to a scrolling input (e.g., rotation ofrotatable input mechanism 604A).

Referring to FIG. 10E, user input (e.g., tap input) 1005 is received,where user input 1005 corresponds to selection of end affordance 1040A.In accordance with a determination that user input 1005 is detected atend affordance 1040A in the scrollable list of affordances 1040, thephysical activity tracking function for the outdoor run is discontinued.That is, execution of the physical activity tracking function for theoutdoor run is stopped in accordance to the selection of end affordance1040A. The selection can cause data to be stored for the outdoor run asa previous workout. It should be recognized that data can be stored forthe outdoor run as the data is detected.

Referring to FIG. 10F, user interface 1044 is displayed in response toselection of end affordance 1040A. User interface 1044 can providefeedback regarding data detected by device 600A for the outdoor run. Forexample, user interface 1044 includes representations 1046 of differenttypes of data detected by device 600A for the outdoor run. In FIG. 10F,representations 1046 include total mileage 1046A (e.g., an indication ofa number of miles traveled during the outdoor run), average pace permile 1046B (e.g., an indication of an average amount of time it hastaken for device 600A to travel a mile during the outdoor run), totaltime 1046C (e.g., an indication of a duration of the outdoor run), totalactive calories 1046D (e.g., an indication of an amount of caloriesdetermined to be burned by the user wearing device 600A during an activestate for the outdoor run), and total calories 1046E (e.g., anindication of an amount of calories determined to be burned by the userwearing device 600A during the outdoor run). It should be recognizedthat, in some examples, user interface 1044 can include more or fewerrepresentations.

User interface 1044 also includes an identification of the outdoor run(e.g., representation 1048), a physical activity icon (e.g., physicalactivity icon 1050), or other information known by device 600A. WhileFIG. 10F depicts a particular visual appearance of representations 1046,it should be recognized that representations can appear differently.

FIG. 10G again illustrates user interface 1004 (as depicted in FIG. 10Aand under circumstances as described with respect to FIG. 10A). Asdescribed above, user interface 1004 includes change affordance 1006B.Referring to FIG. 10G, user input (e.g., tap input) 1003 is received,where user input 1003 corresponds to selection of change affordance1006B. In some examples, when selecting to change a type of workout,data detected prior to selecting change affordance 1006B is notconfigured to be associated with the new type of workout. For example,changing the workout causes a new workout to begin after the new workoutis selected, unlike what occurs (in some examples) when selecting tostart a workout using affordance 1006A) (e.g., data detected prior tostarting the workout using affordance 1006A can be configured to beassociated with the workout). In other words, start affordance 1006Acauses data detected prior to selection of start affordance 1006A to beused and change affordance 1006B causes data detected prior to selectionof change affordance 1006B to not be used. In accordance with adetermination that user input 1003 is detected at change affordance1006B in the scrollable list of affordances 1006, user interface 1030illustrated in FIG. 10H is displayed.

User interface 1030 allows a user to select a different type of workoutfor a current workout. For example, when it is determined that the useris running outside, the user can change the outdoor run to a second typeof workout, indicating that the determination of the outdoor run wasincorrect. When a different type of workout is selected, a physicalactivity tracking function corresponding to the different type ofworkout launches automatically.

User interface 1030 includes a scrollable list of affordances 1032,which are associated with respective physical activity trackingfunctions for a physical activity. For example, the scrollable list ofaffordances 1032 includes affordance 1032A (which corresponds to aphysical activity tracking function for climbing stairs (referred to asstair stepping)), affordance 1032B (which corresponds to a physicalactivity tracking function for an outdoor run), and affordance 1032C(which corresponds to a physical activity tracking function for a walk).It is noted that the scrollable list of affordances 1032 can includeadditional affordances corresponding to other physical activity trackingfunctions that are not currently displayed but can be displayed inresponse to a scrolling input (e.g., rotation of rotatable inputmechanism 604A).

In some examples, each of one or more affordances in the scrollable listof affordances 1032 includes representations 1034 corresponding to aphysical activity associated with the affordance. Representations 1034includes a physical activity icon corresponding to the physical activityassociated with the affordance. For example, affordance 1032A includesphysical activity icon 1034A (e.g., icon of a person climbing stairs).Similarly, affordance 1032C includes physical activity icon 1034D (e.g.,icon of a person walking). In various examples, physical activity iconsare displayed in a first state (e.g., static state).

Representations 1034 further includes a workout identifier. For example,affordance 1032A includes workout identifier 1034B that indicates thataffordance 1032A is associated with a stair stepper workout. Similarly,affordance 1032B includes a workout identifier that indicates thataffordance 1032B is associated with an outdoor run workout.

In some examples, one or more affordances in the scrollable list ofaffordances 1032 includes workout goal information. For example,affordance 1032A includes workout goal information 1034C that indicatesthat the stair stepper workout associated with affordance 1032A has apredetermined goal of twenty minutes. That is, when affordance 1032A isselected, the associated physical activity tracking function willautomatically track information for the stair stepper workout with apreset goal of twenty minutes. Affordance 1032B includes a goal workoutaffordance that indicates that the outdoor run associated withaffordance 1032B is an “open goal.” An open goal indication indicates tothe user that the associated workout does not currently have any presetgoals. Accordingly, when affordance 1032B is selected, various metricswill be tracked by the associated physical activity tracking function,wherein the metrics do not include any preset goal values.

FIG. 10I illustrates a series of states of device 600A withtouch-sensitive display 602A. The series of states depict user interface1004 (which is also depicted in FIG. 10A) over time.

By depicting user interface 1004 over time, it is illustrated howphysical activity icon 1008 can be animated. For example, physicalactivity icon 1008A depicts physical activity icon 1008 in a firststate, physical activity icon 1008B depicts physical activity icon 1008in a second state subsequent to the first state, and physical activityicon 1008C depicts physical activity icon 1008 in a third statesubsequent to the second state.

The animation can give the impression that a person is running.Animating physical activity icon 1008 can provide feedback to a userthat device 600A has determined (e.g., detected) that a workout hasbegun.

FIGS. 10J and 10K illustrate user interfaces displayed in response todeterminations that different types of workouts have begun. For example,different types of workouts can be associated with different sets of oneor more criteria. When a set of one or more criteria for a particulartype of workout is satisfied, a user interface for beginning a workoutcorresponding to the particular type of workout can be displayed.

Referring to FIG. 10J, user interface 1052 of a workout application isdisplayed on touch-sensitive display 602A. User interface 1052 includesa scrollable list of affordances 1054, which is similar (e.g., functionsin a similar manner) to the scrollable list of affordances 1006. Forexample, the scrollable list of affordances 1054 includes startaffordance 1054A (which corresponds to a physical activity trackingfunction for a walk). It is noted that the scrollable list ofaffordances 1054 might not fit within touch-sensitive display 602A; inwhich case one or more affordances not displayed can be displayed inresponse to a scrolling input (e.g., rotation of rotatable inputmechanism 604A).

User interface 1054 further includes physical activity icon 1056corresponding to a physical activity associated with start affordance1054A. Physical activity icon 1056 is an icon of a person walking. Invarious examples, physical activity icon 1056 is displayed in ananimated state.

Referring to FIG. 10K, user interface 1058 of a workout application isdisplayed on touch-sensitive display 602A. User interface 1058 includesa scrollable list of affordances 1060, which is similar (e.g., functionsin a similar manner) to the scrollable list of affordances 1006. Forexample, the scrollable list of affordances 1060 includes startaffordance 1060A (which corresponds to a physical activity trackingfunction for a rowing exercise). It is noted that the scrollable list ofaffordances 1060 might not fit within touch-sensitive display 602A; inwhich case one or more affordances not displayed can be displayed inresponse to a scrolling input (e.g., rotation of rotatable inputmechanism 604A).

User interface 1058 further includes physical activity icon 1062corresponding to a physical activity associated with start affordance1060A. Physical activity icon 1062 is an icon of a person rowing. Invarious examples, physical activity icon 1062 is displayed in ananimated state.

In some examples, instead of displaying user interface 1004, userinterface 1068 is displayed, as depicted in FIG. 10M. In such examples,user interface 1068 is displayed when a determination is made that thereare multiple types of workouts that have potentially begun. Userinterface 1068 includes a scrollable list of affordances 1070, whereeach affordance is associated with a different operation. For example,the scrollable list of affordances 1070 includes start outdoor runaffordance 1070A, start indoor run affordance 1070B, change affordance1070C, and dismiss affordance 1070D. Start outdoor run affordance 1070Acauses a physical activity tracking function configured for outdoor runsto be launched (similar to start affordance 1006A). Start indoor runaffordance 1070B causes a physical activity tracking function configuredfor indoor runs to be launched. Change affordance 1070C allows a user topick a different type of workout such that a physical tracking functionconfigured for the different type of workout is launched (similar tostart affordance 1006B). Dismiss affordance 1070D causes user interface1068 to cease to display (similar to start affordance 1006C).

In some examples, start indoor run affordance 1070B is related to a typeof workout that is an alternative to a type of workout corresponding tostart outdoor run affordance 1070A (in some examples, types of workoutsare related when tracking data used for one can be used for the other).In such examples, start outdoor run affordance 1070A is visuallyhighlighted (e.g., a different color and/or a different size) ascompared to start indoor run affordance 1070B (and in comparison to theother affordances 1070C and 1070D). In some examples, start outdoor runaffordance 1070A is visually highlighted because a determination, basedon sensor data, has been made that it is more likely that a user isrunning outdoor than indoors. In some examples, start indoor runaffordance 1070B is not visually highlighted as compared to changeaffordance 1070C and dismiss affordance 1070D. In other words, startindoor run affordance 1070B, change affordance 1070C, and dismissaffordance 1070D can appear similar while start outdoor run affordance1070A is visually distinct from all three. Examples of types of workoutsthat might commonly be paired together as a main workout and analternative workout include outdoor/indoor run, outdoor/indoor walk, andpool swim/open water swim. While only a single alternative isillustrated in FIG. 10M, it should be recognized that more than onealternative may be included in the scrollable list of affordances 1070.

In some examples, after an alert is issued (e.g., user interface 1004),a user interface (e.g., user interface 1076) for selecting to start aworkout from a list of workouts includes one or more representationscorresponding to the alert, as depicted in FIGS. 10P-10Q and discussedbelow. Such a user interface can be navigated to as depicted in FIGS.10N-10O and discussed below.

FIG. 10N illustrates user interface 1072 displayed on touch-sensitivedisplay 602A of device 600A. User interface 1072 includes multipleapplication affordances 1074 associated with applications. For example,affordance 1074A is associated with an audio application and affordance1074B is associated with a workout application. In some examples, userinterface 1072 can be displayed to present which application can belaunched using device 600A. Selection of an affordance included in userinterface 1072 can cause a corresponding application to be launched.

FIG. 10O again illustrates user interface 1072 (as depicted in FIG.10N). As described above, user interface 1072 includes affordance 1074B.Referring to FIG. 10O, user input (e.g., tap input) 1007 is received,where user input 1007 corresponds to selection of affordance 1074B. Inaccordance with a determination that user input 1007 is detected ataffordance 1074B, the workout application that corresponds to affordance1074B is launched and user interface 1076 (which is discussed below anddepicted in FIG. 10P) is displayed.

Referring to FIG. 10P, user interface 1076 includes a scrollable list ofaffordances 1078, which are associated with respective physical activitytracking functions for respective physical activities. In some examples,the scrollable list of affordances 1078 includes at least two types ofaffordances: a first type of affordance associated with physicalactivity tracking functions corresponding to an alert (e.g., userinterface 1004) issued by device 600A; and a second type of affordance(e.g., 1078C) associated with physical activities that are track-able bydevice 600A (but do not correspond to an alert (e.g., 1004) issued bydevice 600A). In some examples, physical activities are represented inboth the first type and the second type such that the scrollable list ofaffordances 1078 includes (1) a first affordance (of a first type ofaffordance) associated with a particular type of physical activity and(2) a second affordance (of a second type of affordance different fromthe first type of affordance) associated with the particular type ofphysical activity. In other examples, physical activities represented bythe first type of affordance are not represented by the second type ofaffordance.

As depicted in FIG. 10P, the scrollable list of affordances 1078includes multiple affordances of the first type of affordance:affordance 1078A (which corresponds to continuing a physical activitytracking function for an outdoor run that began at 10 AM) and affordance1078B (which corresponds to continuing a physical activity trackingfunction for an indoor run that began at 10 AM). The scrollable list ofaffordances 1078 includes multiple affordances of the first type ofaffordance in response to either (1) multiple different alerts (e.g.,user interface 1004) have been issued without initiating a physicalactivity tracking function corresponding to one of the multipledifferent alerts or (2) an alert with multiple types of workouts (e.g.,user interface 1068) has been issued without initiating a physicalactivity tracking function corresponding to one of the multiple types ofworkouts.

It should be noted that user interface 1076 includes a clock indicatingthat the time is “10:09” and affordance 1078A indicates a workoutstarting at 10 AM. This illustrates that selection of affordance 1078Acauses data tracked since 10 AM to be recorded for a current outdoorrunning workout even though a user did not indicate to begin an outdoorrunning workout at 10 AM.

In some examples, the scrollable list of affordances 1078 can includeadditional affordances corresponding to other physical activity trackingfunctions that are not currently displayed but can be displayed inresponse to a scrolling input (e.g., rotation of rotatable inputmechanism 604A). FIG. 10Q depicts user interface 1076 in response to ascrolling input. User interface 1076 in FIG. 10Q again includes thescrollable list of affordances 1078.

As depicted in FIG. 10Q, the scrollable list of affordances 1078includes an affordance of the first type of affordance (i.e., affordance1078B) and multiple affordances of the second type of affordance, themultiple affordances including: affordance 1078C (which corresponds to aphysical activity tracking function for a stair stepping workout) andaffordance 1078D (which corresponds to a physical activity trackingfunction for a walk). The scrollable list of affordances 1206 isconfigured such that a type of physical activity can be selected for acurrent workout. In some examples, when an affordance of the first typeof affordance is selected, a workout is started using data detectedbefore selection of the affordance. In such examples, when a affordanceof the second type of affordance is selected, a workout is started thatdoes not use data detect before selection of the affordance (only datadetected after selection of the affordance). In some examples,affordances of the first type of affordance (e.g., affordance 1078A andaffordance 1078B) are visually highlighted as compared to affordances ofthe second type of affordance (e.g., affordance 1078C and affordance1078D).

FIG. 11 is a flow diagram illustrating a method for displaying an alertin response to automatically determining a boundary of physical activityusing an electronic device in accordance with some examples. Method 1100is performed at a device (e.g., 100, 300, 500, 600A, 600B, 800) with adisplay and one or more sensors (e.g., a gyroscope, a camera, anaccelerometer, GPS sensor, heart rate monitor, clock, the like, or anycombination thereof. Some operations in method 1100 are, optionally,combined, the orders of some operations are, optionally, changed, andsome operations are, optionally, omitted.

As described below, method 1100 provides an intuitive way for displayingan alert in response to automatically determining a boundary of physicalactivity (e.g., a workout). The method reduces the cognitive burden on auser for starting and stopping a physical activity tracking function,thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to track activitydata faster and more efficiently conserves power and increases the timebetween battery charges.

At 1102, the device (e.g., 600A) detects, via the one or more sensors,activity data (e.g., heart rate data, GPS data, movement data, or thelike) (e.g., FIG. 10A, data detected to cause user interface 1004 to bedisplayed). In some examples, the one or more sensors used to detect theactivity data are a subset of sensors included with the electronicdevice (e.g., some sensors may not be used to detect the activity data).

In some examples, the activity data is detected before a physicalactivity tracking function is active (e.g., a tracking functioncorresponding to 1026). In such examples the activity data is used todetermine whether to initiate a physical activity tracking function(e.g., the boundary condition is a start of a workout).

At 1102, in response to detecting the activity data, in accordance witha determination that the activity data satisfies activity boundary alertcriteria (e.g., criteria for categorizing activity data as correspondingto a boundary (e.g., a start, an end, a transition from one type ofactivity to another) of user activity (e.g., a user workout)), thedevice (e.g., 600A) displays an activity boundary alert (e.g., a userinterface including a confirmation affordance and an indication of thetype of activity boundary detected) (e.g., 1004 or 1038). Displaying anactivity boundary alert provides feedback as to when a device detects anactivity boundary. Providing improved feedback and performing anoperation when a set of conditions has been met without requiringfurther user input enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some examples, the activity boundary alert (e.g., 1004) includes afirst affordance (e.g., 1006A). In such examples, the device (e.g.,600A) receives a first user input (e.g., 1001) corresponding toselection of the first affordance. In response to receiving the firstuser input, the device initiates a physical activity tracking function(e.g., user interface 1026 can be displayed with information fromphysical activity tracking function) corresponding to a type of physicalactivity (e.g., running, HIIT, yoga, or the like) corresponding to theactivity boundary alert (e.g., the physical tracking functionscorresponds to the first affordance). In some examples, the activityboundary alert includes a third affordance (e.g., 1006C). In suchexamples, selection of the third affordance causes the device to forgoinitiating the physical activity tracking function corresponding to atype of physical activity corresponding to the activity boundary alert.In such examples, the device continues to determine when a workoutbegins.

In some examples, the physical activity tracking function correspondingto the activity boundary alert (e.g., 1004) tracks activity datadetected prior to displaying the activity boundary alert.

In some examples, the activity boundary alert (e.g., 1004) correspondsto a first physical activity tracking function (e.g., an activitytracking function corresponding to a predicted type of activity (e.g.,running, swimming, rowing)). In such examples, the activity boundaryalert includes a second affordance (e.g., 1006). In such examples, thedevice receives a second user input (e.g., 1003) corresponding toselection of the second affordance in the activity boundary alert. Inresponse to receiving the second user input, the device displays a firstuser interface (e.g., 1030) including: a third affordance (e.g., 1032A)corresponding to a second physical activity tracking function differentthan the first physical activity tracking function; and a fourthaffordance (e.g., 1032C) corresponding to a third physical activitytracking function different than the first physical activity trackingfunction. While displaying the first user interface the device receivesa third user input. In accordance with the third user inputcorresponding to selection of the third affordance in the first userinterface, the device configures the electronic device to track activitydata detected after selection of the third affordance using the secondphysical activity tracking function. In accordance with the third userinput corresponding to selection of the fourth affordance in the seconduser interface, the device configures the electronic device to trackactivity data detected after selection of the fourth affordance usingthe third physical activity tracking function. In some examples, theactivity boundary alert includes an animated affordance (e.g., FIG. 10I)representing a type of workout associated with the activity boundaryalert.

In some examples, the activity data was detected via a first sensor ofthe one or more sensors. In such examples, initiating the physicalactivity tracking function corresponding to the type of physicalactivity corresponding to the activity boundary alert (e.g., thephysical tracking functions corresponds to the first affordance)includes detecting second activity data via a second sensor, differentthan the first sensor (e.g., the first sensor is an accelerometer andthe second sensor is a GPS sensor), of the one or more sensors. In someexamples, the second sensor is activated, from an inactive state.

In some examples, the activity data is detected while an existingphysical activity tracking function is active (e.g., a tracking functioncorresponding to 1026).

In some examples, the activity data is detected while an existingphysical activity tracking function is active. For example, the deviceis already tracking a workout. In such examples, the activity boundaryalert (e.g., 1038) includes a fifth affordance (e.g., 1040A). In suchexamples, the device receives a first fourth input (e.g., 1005)corresponding to selection of the fifth affordance. In response toreceiving the fourth user input, the device ends the current physicalactivity tracking function. In further response to receiving the fourthuser input, the device stores activity data (e.g., including theactivity data) detected prior to receiving the fourth user input as aprevious workout.

In some examples, the activity boundary alert (e.g., 1038) includes asixth affordance (e.g., 1040B). In such examples, the device receives afifth user input corresponding to selection of the sixth affordance. Inresponse to receiving the fifth user input, the device pauses executionof a physical activity tracking function. In some examples, the activityboundary alert includes a dismiss affordance (e.g., 1040D) to not stoprecording a workout.

In some examples, the activity boundary alert (e.g., 1038) correspondsto a first physical activity tracking function. In such examples, theactivity boundary alert includes a seventh affordance (e.g., 1040C). Insuch examples, the device receives a sixth user input (e.g., similar to1003) corresponding to selection of the seventh affordance. In responseto receiving the sixth third input, the device initiates a process forceasing execution of a first physical activity tracking function. Infurther response to receiving the sixth third input, the device displaysa second user interface (e.g., 1030) including: an eighth affordance(e.g., 1032A) corresponding to a second physical activity trackingfunction different than the first physical activity tracking function,and a ninth affordance (e.g., 1032C) corresponding to a third physicalactivity tracking function different than the first physical activitytracking function. In such examples, the device receives a seventh userinput. In accordance with the seventh user input corresponding toselection of the eighth affordance in the second user interface, thedevice initiates the second physical activity tracking function. Inaccordance with the seventh user input corresponding to selection of theninth affordance in the second user interface, the device initiates thethird physical activity tracking function.

In some examples, the activity boundary alert includes a staticaffordance (e.g., FIG. 10G, icon of running man) representing a type ofworkout associated with the activity boundary alert.

In some examples, the determination that the activity data satisfiesactivity boundary alert criteria can update over time based upon userinteractions.

In some examples, the activity boundary alert (e.g., 1068) includes atenth affordance (e.g., 1070B) (in some examples, the tenth affordanceis an affordance for an alternative type of workout as compared to thefirst affordance (e.g., 1070A)), and wherein the physical activitytracking function corresponding to the activity boundary alert is afirst physical activity tracking function. In such examples, theelectronic device receives an eighth user input corresponding toselection of the tenth affordance and, in response to receiving theeighth user input, initiates a second physical activity trackingfunction corresponding to the activity boundary alert, wherein thesecond physical activity tracking function is different from the firstphysical activity tracking function (in some examples, each of the firstphysical activity tracking function and the second physical activitytracking function uses the activity data in a first manner (e.g.,tracking number of miles) while a third physical activity trackingfunction that does not correspond to the activity boundary alertcriteria uses the activity data in a second manner different from thefirst manner (e.g., tracking number of laps)).

In some examples, the first affordance (e.g., 1070A) and the tenthaffordance (e.g., 1070B) are ordered based upon which respective workoutis determined to be more likely the type of workout being performed. Forexample, if a determination is made that it is more likely that a useris performing an outdoor run than an indoor run, an affordanceassociated with an outdoor run precedes an affordance associated with anindoor run, as illustrated in FIG. 10M.

In some examples, the first affordance is highlighted as compared to thetenth affordance, to highlight that a workout corresponding to the firstaffordance has been determined to be more likely being performed than aworkout corresponding to the tenth affordance.

In some examples, wherein the activity boundary alert is a firstactivity boundary alert (e.g., 1064) including (in some examples, theactivity boundary alert is displayed in response to a short look) firstcontent, after displaying the first activity boundary alert, theelectronic device displays a second activity boundary alert (e.g., 1004)(in some examples, the second activity boundary alert is displayed inresponse to a long look) including second content, wherein the secondcontent is different from the first content (e.g., the second contentincludes the first content and additional content) (in some examples,the second activity boundary alert is displayed in accordance with adetermination that look criteria have been satisfied).

At 1106, in further response to detecting the activity data and inaccordance with a determination that the activity data does not satisfythe activity boundary alert criteria, the device forgoes display of theactivity boundary alert (e.g., forgoes displaying 1004).

In some examples, further in response to detecting the activity data andin accordance with a determination that the activity data satisfiessecond activity boundary alert criteria, the device displays a secondactivity boundary alert (e.g., alert 1058), where the activity boundaryalert criteria and the activity boundary alert (e.g., alert 1004) relateto a first type of physical activity (e.g., running), and where thesecond activity boundary alert criteria and the second activity boundaryalert relate to a second type of physical activity (e.g., rowing)different than the first type. In accordance with a determination thatthe activity data does not satisfy the second activity boundary alertcriteria, the device forgoes display of the second activity boundaryalert (e.g., forgoes displaying 1004).

In some examples, where the activity boundary alert is a first activityboundary alert, after a predetermined time (e.g., 3 minutes) has lapsedwithout initiating a physical activity tracking function correspondingto the first activity boundary alert, the electronic device displays asecond activity boundary alert (e.g., 1004), wherein a physical activitytracking function corresponding to the second activity boundary alerttracks activity data detected prior to displaying the first activityboundary alert.

In some examples, after displaying the activity boundary alert andbefore a physical activity tracking function is active, the electronicdevice displays a third user interface (e.g., 1076) (in some examples,the third user interface is the first user interface) including ascrollable list of affordances (e.g., 1078) associated with physicalactivities. In some examples, the electronic device receives a ninthuser input. In some examples, in accordance with a determination thatthe ninth user input is detected at an eleventh affordance (e.g., 1078A)in the scrollable list of affordances, the electronic device launches aphysical activity tracking function corresponding to the activityboundary alert (in some examples, the physical activity trackingfunction associated corresponding to the activity boundary alert tracksactivity data detected prior to displaying the third user interface) (insome examples, the physical activity tracking function corresponding tothe activity boundary alert tracks activity data detected prior todisplaying the activity boundary alert). In some examples, in accordancewith a determination that the ninth user input is detected at a twelfthaffordance (e.g., 1078C) in the scrollable list of affordances, theelectronic device launches a physical activity tracking function (1) notcorresponding to the activity boundary alert and (2) different from thephysical activity tracking function corresponding to the activityboundary alert. In some examples, wherein the physical activity trackingfunction corresponding to the activity boundary alert is a first thephysical activity tracking function, in accordance with a determinationthat the ninth user input is detected at a thirteenth affordance (e.g.,1078B) in the scrollable list of affordances, the electronic devicelaunches a second physical activity tracking function corresponding tothe activity boundary alert, wherein the second physical activitytracking function is different from the first physical activity trackingfunction, and wherein the second physical activity tracking functioncorresponding to the activity boundary alert tracks activity datadetected after receiving the ninth user input (in some examples, thesecond physical activity tracking function tracks activity data detectedafter launching the second physical activity tracking function) (in someexamples, one of the physical activity tracking functions correspondingto with the eleventh or twelfth affordance is the same physical activitytracking function corresponding to the thirteenth affordance).

In some examples, the eleventh affordance and the thirteenth affordanceare visually highlighted (e.g., different color and/or bigger) ascompared to the twelfth affordance, to indicate that the eleventhaffordance and the thirteenth affordance are a different type ofaffordance from the twelfth affordance.

Note that details of the processes described above with respect tomethod 1100 (e.g., FIG. 11) are also applicable in an analogous mannerto the methods described below/above. For example, method 1100optionally includes one or more of the characteristics of the variousmethods described below with reference to method 700, method 900, ormethod 1300. For example, in response to the user interface of method1100, the user interface of method 700 can be displayed. For anotherexample, the user interface of method 1100 can lead (e.g., ending aworkout can cause activity data to be generated) to the user interfaceof method 900 being displayed in response to activity data generated.For another example, a pace set using method 1100 can cause the userinterface of method 1300 to be displayed. For brevity, these details arenot repeated below.

FIGS. 12A-12AK illustrate exemplary user interfaces associated withconfiguring a pace alert for a workout application in accordance withsome examples. The user interfaces allow a user to configure the datasetused to calculate a pace for the pace alert. For example, the datasetused can include data starting from the beginning of a workout (referredto as an average). For another example, the dataset used can be aprevious amount of data relative to a current time such that the datasetdoes not include data from the beginning of the workout (referred to asa rolling average). The user interfaces in these figures are used toillustrate the processes described below, including the processes inFIG. 13.

FIG. 12A illustrates user interface 1256 displayed on touch-sensitivedisplay 602A of device 600A. User interface 1256 includes multipleapplication affordances 1258 associated with applications. For example,affordance 1258A is associated with an audio application and affordance1258B is associated with a workout application. In some examples, userinterface 1256 can be displayed to present which application can belaunched using device 600A. Selection of an affordance included in userinterface 1256 can cause a corresponding application to be launched.

FIG. 12B again illustrates user interface 1256 (as depicted in FIG.12A). As described above, user interface 1256 includes affordance 1258B.Referring to FIG. 12B, user input (e.g., tap input) 1229 is received,where user input 1229 corresponds to selection of affordance 1258B. Inaccordance with a determination that user input 1229 is detected ataffordance 1258B, the workout application that corresponds to affordance1258B is launched and user interface 1204 (which is discussed below anddepicted in FIG. 12C) is displayed.

Referring to FIG. 12C, user interface 1204 includes a scrollable list ofaffordances 1206, which are associated with respective physical activitytracking functions for respective physical activities. For example, thescrollable list of affordances 1206 includes affordance 1206A (whichcorresponds to a physical activity tracking function for an outdoorrun), affordance 1206B (which corresponds to a physical activitytracking function for an indoor cycling workout), and affordance 1206C(which corresponds to a physical activity tracking function for a walk).In some examples, the scrollable list of affordances 1206 can includeadditional affordances corresponding to other physical activity trackingfunctions that are not currently displayed but can be displayed inresponse to a scrolling input (e.g., rotation of rotatable inputmechanism 604A). The scrollable list of affordances 1206 is configuredsuch that a type of physical activity can be selected for a currentworkout.

In some examples, one or more affordances in the scrollable list ofaffordances 1206 includes an options affordance, as further discussedbelow. For example, affordance 1206A includes options affordance 1208.

Referring to FIG. 12D, user input (e.g., tap input) 1201 is received,where user input 1201 corresponds to selection of options affordance1208. In accordance with a determination that user input 1201 isdetected at options affordance 1208, a user interface (e.g., userinterface 1210 as depicted in FIG. 12E) is displayed with optionsrelated to a physical activity corresponding to affordance 1206A.

Referring to FIG. 12E, user interface 1210 is displayed in response toselection of options affordance 1208 (as depicted in FIG. 12D). Userinterface 1210 provides options to change how device 600A operates whenexecuting a physical activity tracking function corresponding toaffordance 1206A. User interface 1210 includes back affordance 1212 tocause user interface 1204 (as depicted in FIG. 12C) to be displayed.User interface 1210 further includes pace-alert affordance 1214 to allowa user to configure a pace alert for the physical activity trackingfunction corresponding to affordance 1206A.

FIG. 12F again illustrates user interface 1210 (as depicted in FIG.12E). As described above, user interface 1210 includes pace-alertaffordance 1214. Referring to FIG. 12F, user input (e.g., tap input)1203 is received, where user input 1203 corresponds to selection ofpace-alert affordance 1214.

In some examples, in accordance with a determination that user input1203 is detected at pace-alert affordance 1214, a user interface (e.g.,user interface 1216 as depicted in FIG. 12G) is displayed with optionsrelated to a pace alert. In other examples, in accordance with adetermination that user input 1203 is detected at pace-alert affordance1214, a user interface (e.g., user interface 1222 as depicted in FIG.12I) is displayed with options related to setting a pace for a pacealert.

Referring to FIG. 12G, user interface 1216 is displayed in response toselection of pace-alert affordance 1214. User interface 1216 providesoptions to configure a pace alert. User interface 1216 includes backaffordance 1220 to cause user interface 1210 (as depicted in FIG. 12E)to be displayed.

User interface 1216 further includes a scrollable list of affordances1218, which are associated with different operations. For example, thescrollable list of affordances 1218 includes set-pace affordance 1218A(which corresponds to causing a display for setting a pace to bedisplayed), average affordance 1218B (which corresponds to causing apace to be calculated using data from an entire workout), rollingaffordance 1218C (which corresponds to causing a pace to be calculatedusing a subset of data from a workout, where the subset is less than theentire workout), off affordance 1218D (which corresponds to turning offa pace alert), or any combination thereof. It is noted that, in someexamples, the scrollable list of affordances 1218 might not fit withintouch-sensitive display 602A; in which case one or more affordances notdisplayed can be displayed in response to a scrolling input (e.g.,rotation of rotatable input mechanism 604A).

As used herein, pace can refer to speed (e.g., an amount of distancethat a device travels in an amount of time or an amount of time that ittakes for a device to travel an amount of distance). In regards to pace,the different calculations described herein (e.g., average and rolling)can refer to changing an amount of a dataset for a current workout thatis used when performing a pace calculation. For example, for average,the pace calculation can be based upon data detected during the entirecurrent workout. For rolling, the pace calculation can be based upondata detected during an amount prior to a current location (e.g., datadetected for the last mile or data detected for the last 5 minutes).

FIG. 12H again illustrates user interface 1216 (as depicted in FIG.12G). As described above, user interface 1216 includes set-paceaffordance 1218A. Referring to FIG. 12H, user input (e.g., tap input)1205 is received, where user input 1205 corresponds to selection ofset-pace affordance 1218A. In accordance with a determination that userinput 1205 is detected at set-pace affordance 1218A, a user interface(e.g., user interface 1222 as depicted in FIG. 12I) is displayed withoptions related to setting a pace for a pace alert.

Referring to FIG. 12I, user interface 1222 can be displayed in responseto selection of set-pace affordance 1218A (as depicted in FIG. 12H) insome examples. In other examples, user interface 1222 can be displayedin response to selection of pace-alert affordance 1214 in user interface1210 (as depicted in FIG. 12E). User interface 1222 can provide optionsto allow a user to set a pace for a pace alert. User interface 1222 caninclude back affordance 1228 to cause user interface 1210 to bedisplayed.

User interface 1222 further includes multiple affordances for setting atime (e.g., minutes-setting affordance 1224A and seconds-settingaffordance 1224B). Minutes-setting affordance 1224A is used to set anumber of minutes for a pace. Seconds-setting affordance 1224B is usedto set a number of seconds for the pace.

As depicted in FIG. 12I, each affordance for setting the time isindependently selectable. For example, each of minutes-settingaffordance 1224A and seconds-setting affordance 1224B can be selected.When an affordance of the multiple affordances for setting a time isselected, the affordance can be visually distinguished. For example, inFIG. 12I, minutes-setting affordance 1224A has a thicker border thanseconds-setting affordance 1224B, indicating minutes-setting affordance1224A is selected (e.g., in focus).

User interface 1222 further includes a scrollable list of affordances1226, which are each associated with different operations. For example,the scrollable list of affordances 1226 includes set-pace affordance1226A (which corresponds to setting a pace identified using the multipleaffordances for setting a time) and cancel affordance 1226B (whichcorresponds to displaying a user interface for providing options toconfigure a pace alert, such as user interface 1216 in FIG. 12G), or anycombination thereof. It is noted that, in some examples, the scrollablelist of affordances 1226 might not fit within touch-sensitive display602A; in which case one or more affordances not displayed can bedisplayed in response to a scrolling input (e.g., rotation of rotatableinput mechanism 604A).

FIG. 12J again illustrates user interface 1222 (as depicted in FIG.12I). As described above, user interface 1222 includes seconds-settingaffordance 1224B. Referring to FIG. 12J, user input (e.g., tap input)1207 is received, where user input 1207 corresponds to selection ofseconds-setting affordance 1224B. In accordance with a determinationthat user input 1207 is detected at seconds-setting affordance 1224B,seconds-setting affordance 1224B can be visually distinguished fromminutes-setting affordance 1224A. For example, selection ofseconds-setting affordance 1224B can cause seconds-setting affordance1224B to be visually distinguished instead of minutes-setting affordance1224A.

FIG. 12K again illustrates user interface 1222. Referring to FIG. 12K,seconds-setting affordance 1224B is visually distinguished instead ofminutes-setting affordance 1224A. In particular, seconds-settingaffordance 1224B has a thicker border than minutes-setting affordance1224A, indicating seconds-setting affordance 1224B is selected (e.g., infocus).

FIG. 12L depicts an example of user interface 1222 for scrolling ofseconds-setting affordance 1224B. Referring to FIG. 12L, rotationalinput 1209 is received at rotatable input mechanism 604A. In response torotational input 1209, options for seconds-setting affordance 1224B isscrolled in an upward direction such that different options forseconds-setting affordance 1224B are displayed, as depicted in FIG. 12M.For example, FIG. 12M depicts user interface 1222 changingseconds-setting affordance 1224B from “30” (as depicted in FIG. 12L) to“29” (as depicted in FIG. 12M). Similar scrolling can occur whenminutes-setting affordance 1224A is selected and rotational input 1209is received. Scrolling the opposite direction for both affordances mayalso be performed.

FIG. 12N again illustrates user interface 1222 (as depicted in FIG.12M). As described above, user interface 1222 includes set-paceaffordance 1226A. Referring to FIG. 12N, user input (e.g., tap input)1211 is received, where user input 1211 corresponds to selection ofset-pace affordance 1226A. In accordance with a determination that userinput 1211 is detected at set-pace affordance 1226A, a user interface(e.g., user interface 1216 as depicted in FIG. 12O) is displayed withoptions related to a pace alert.

Referring to FIG. 12O, user interface 1216 can be displayed in responseto selection of set-pace affordance 1226A. User interface 1216 canprovide options to change how device 600A operates when executing aphysical activity tracking function corresponding to affordance 1206A.As depicted in FIG. 12O, user interface 1216 can include a scrollablelist of affordances 1218, which are associated with differentoperations. Text in set-pace affordance 1218A (as depicted in FIG. 12O)has been changed from “Set Pace” (as depicted in FIG. 12G) to a pace setby a user (e.g., “8′29″ MI”), such as the pace set in FIG. 12N.

As discussed above, the scrollable list of affordances 1218 includesaverage affordance 1218B. Referring to FIG. 12P, user input (e.g., tapinput) 1213 is received, where user input 1213 corresponds to selectionof average affordance 1218B, causing the physical activity trackingfunction corresponding to affordance 1206A to use an averagecalculation.

FIG. 12Q illustrates user interface 1216 in response to selection ofaverage affordance 1218B. Referring to FIG. 12Q, average affordance1218B is updated to include an indication (e.g., a check mark) that apace will be calculated according to an average operation.

Referring to FIG. 12R, user input (e.g., tap input) 1215 is received,where user input 1215 corresponds to selection of back affordance 1220.In some examples, in accordance with a determination that user input1215 is detected at back affordance 1220, a user interface (e.g., userinterface 1210 as depicted in FIG. 12S) is displayed with options tochange how device 600A operates when executing a physical activitytracking function corresponding to affordance 1206A.

Referring to FIG. 12S, user interface 1210 can be displayed in responseto selection of back affordance 1220. User interface 1210 can provideoptions to change how device 600A operates when executing a physicalactivity tracking function corresponding to affordance 1206A. Text inpace-alert affordance 1214 (as depicted in FIG. 12S) has been updated toinclude an indication of a pace set by a user (e.g., “8′29″ MI AVG”, asdepicted at 1214A). In some examples, The text can be in the updatedstate any time device 600A is navigated to user interface 1210. Byincluding “MI AVG” in the text, pace-alert affordance 1214 can indicatethat the pace alert for a physical activity tracking functioncorresponding to affordance 1206A will be calculated using an averageoperation, as discussed herein.

FIG. 12T again illustrates user interface 1210. Referring to FIG. 12T,user input (e.g., tap input) 1217 is received, where user input 1217corresponds to selection of back affordance 1212. In some examples, inaccordance with a determination that user input 1217 is detected at backaffordance 1212, a user interface (e.g., user interface 1204 as depictedin FIG. 12U) is displayed.

Referring to FIG. 12U, affordance 1206A is updated to include anindication of a pace set by a user (e.g., “8′29″ AVG PACE”, as depictedat 1208B). It should be recognized that multiple affordances in the listof affordances 1206 can include a pace set by a user. In some examples,different affordances in the list of affordances 1206 can includedifferent paces set by a user.

FIG. 12V again illustrates user interface 1204. Referring to FIG. 12V,user input (e.g., tap input) 1219 is received, where user input 1219corresponds to selection of affordance 1206A. In accordance with adetermination that user input 1219 is detected at affordance 1206A inthe scrollable list of affordances 1206, a physical activity trackingfunction configured for outdoor runs is launched. The physical activitytracking function can include a pace alert when a user is below, ontarget, or above a user-specified pace for outdoor runs. Theuser-specified pace, as depicted in FIG. 12V is “8′29″”.

In response to selection of affordance 1206A, user interface 1250 (whichis depicted in FIG. 12W) is displayed. User interface 1250 displays(e.g., provides feedback regarding) data detected by device 600A for anoutdoor run. To display the data detected by device 600A, user interface1250 includes representations 1252. In FIG. 12W, representations 1252include icon 1252A (e.g., an animated icon of a running man to representthe outdoor run), total mileage 1252B (e.g., an indication of a numberof miles traveled during the outdoor run), total calories 1252C (e.g.,an indication of an amount of calories determined to be burned by theuser during the outdoor run), average pace per mile 1252D (e.g., anindication of an average amount of time it has taken for device 600A totravel a mile during the outdoor run), total time 1252E (e.g., anindication of a duration of the outdoor run), and BPM 1252F (e.g., acalculated number of beats per minute for a heart of a user wearingdevice 600A). It should be recognized that, in some examples, userinterface 1250 can include more or fewer representations, similar to asdepicted in FIG. 12AK and discussed below.

While a user is performing the outdoor run, a pace of the user mightgoes above a pace set for the outdoor run. When the pace of the user isabove the pace set for the outdoor run, an alert that the pace of theuser is above the pace set for the outdoor run can be displayed, asdepicted in FIG. 12X.

Referring to FIG. 12X, the alert can be included in user interface 1244.The alert can include an icon corresponding to a current workout andinformation 1246. Information 1246 can include status 1246A and currentpace 1246B. Status 1246A can indicate whether the user is below, ontarget, or above a pace set for the current workout. Referring to FIG.12X, status 1246A indicates that the user is “above target pace”.Current pace 1246B can indicate a current pace for the user. Forexample, current pace 1246B (as depicted in FIG. 12X) indicates that theuser is currently running at a “8′52″” pace, which (due to average beingselected for calculating the pace) is calculated over the entire currentworkout. Because “8′52″” is above the pace set at “8′29″”, the “abovetarget pace” text can be displayed

In response to the user running quicker and bringing their pace to“8′29″”, user interface 1244 can be updated to reflect that the user ison target pace. Referring to FIG. 12Y, status 1246A can be updated toindicate that the user in “on target pace” and current pace 1246B can beupdated to indicate that the user's current pace is “8′29″” whencalculated over the entire current workout.

In response to the user running even quicker and bringing their pace to“7′57″”, user interface 1244 can be updated to reflect that the user isbelow target pace. For example, status 1246A can be updated to indicatethat the user in “on target pace” and current pace 1246B can be updatedto indicate that the user's current pace is “7′57″” when calculated overthe entire current workout. It should be recognized that what valuesconstitute below, on target, and above a target pace can include one ormore values around a target pace. For example, a number of seconds aboveand below target pace can still be considered on target.

In some examples, interface 1244 (as depicted in each of FIG. 12X-12Z)can be displayed to the user once after it is determined that the useris below, on target, or above a target pace. The one time can be when auser brings device 600A into a position to look at device 600A. In suchexamples, additional views of device 600A while the same alert isapplicable can cause user interface 1250 (as depicted in FIG. 12W) to bedisplayed. When user interface 1250 is displayed after an alert, averagepace per mile 1252D can be visually highlighted such that it can easilybe located on user interface 1250.

Referring back to after set-pace affordance 1226A is selected (asdepicted in FIG. 12N), FIG. 12AA again illustrates user interface 1216.While average affordance 1218B is illustrated without a check mark inFIG. 12AA, it should be recognized that average affordance 1218B caninclude the check mark (as depicted in FIG. 12Q).

Referring to FIG. 12AA, user interface 1216 can include rollingaffordance 1218C. Rolling affordance 1218C can correspond to calculatinga pace using a rolling average during a physical activity. Rollingaverage can relate to using a subset of data for the physical activity.For example, while an average for the physical activity might use datafrom a beginning point to a present point of the physical activity, arolling average can use an amount before the present point such that notall of the data from the beginning is used.

In one illustrative example, the user can run 2 miles in 10 minutes. Theaverage for the run would be 5 minutes per mile. If the rolling averageis calculated for the last 5 minutes, the rolling average for the runwould be 5 divided by however much distance was covered in the last 5minutes. For example, if the user ran 1.2 miles in the last 5 minutes,the rolling average for the user is 5 divided by 1.2 (i.e., 4 minutesand 10 seconds per mile).

Referring to FIG. 12AA, user input (e.g., tap input) 1221 is received,where user input 1221 corresponds to selection of rolling affordance1218C. In accordance with a determination that user input 1221 isdetected at rolling affordance 1218C in the scrollable list ofaffordances 1218, user interface 1230 can be displayed, as depicted inFIG. 12AB.

Referring to FIG. 12AB, user interface 1230 includes a list ofaffordances 1232 for configuring how a rolling calculation will beperformed. The list of affordances 1232 can include first affordance1232A and second affordance 1232B. First affordance 1232A corresponds todistance such that the rolling calculation includes data detected for aprevious amount of distance. For example, an average can be calculatedfor data detected in the last mile. Selection of first affordance 1232Acan cause a user interface (e.g., user interface 1236 as depicted inFIG. 12AD and discussed below) to be displayed to allow the user toselect an amount of distance. Second affordance 1232B corresponds totime such that the rolling calculation includes data detected for aprevious amount of time. For example, an average can be calculated fordata detected in the last 5 minutes. Selection of second affordance1232B can cause a user interface (e.g., similar to user interface 1222as depicted in FIG. 12I) to be displayed to allow the user to select anamount of time.

FIG. 12AC again illustrates user interface 1230. As described above forFIG. 12AB, user interface 1230 includes first affordance 1232A, whichcorresponds to distance. Referring to FIG. 12AC, user input (e.g., tapinput) 1223 is received, where user input 1223 corresponds to selectionof first affordance 1232A. In accordance with a determination that userinput 1223 is detected at first affordance 1232A in the scrollable listof affordances 1232, a user interface (user interface 1236 as depictedin FIG. 12AD) for selecting a distance is displayed.

Referring to FIG. 12AD, user interface 1236 can be displayed in responseto selection of first affordance 1232A in user interface 1230. Userinterface 1236 includes multiple affordances 1238 for setting a rollingpace (e.g., integer-setting affordance 1238A and decimal-settingaffordance 1238B). Integer-setting affordance 1238A is used to set anumber of previous whole miles to use for the rolling pace.Decimal-setting affordance 1224B is used to set a number of previousfractional miles to use for the rolling pace.

As depicted in FIG. 12AD, each affordance for setting the rolling paceis independently selectable. For example, each of integer-settingaffordance 1238A and decimal-setting affordance 1238B can be selected.When an affordance of multiple affordances 1238 for setting the rollingpace is selected, the affordance can be visually distinguished. Forexample, in FIG. 12AD, integer-setting affordance 1238A has a thickerborder than decimal-setting affordance 1238B, indicating integer-settingaffordance 1238A is selected (e.g., in focus).

User interface 1236 further includes a scrollable list of affordances1240, which are associated with different operations. For example, thescrollable list of affordances 1240 includes set-pace affordance 1240A(which corresponds to setting a pace identified using the multipleaffordances for setting the rolling pace) and cancel affordance 1240B(which corresponds to displaying a user interface for providing optionsto configure a pace alert, such as user interface 1230 in FIG. 12AB), orany combination thereof. It is noted that the scrollable list ofaffordances 1240 might not fit within touch-sensitive display 602A; inwhich case one or more affordances not displayed can be displayed inresponse to a scrolling input (e.g., rotation of rotatable inputmechanism 604A).

Referring to FIG. 12AE, user input (e.g., tap input) 1225 is received,where user input 1225 corresponds to selection of set-pace affordance1240A. In accordance with a determination that user input 1225 isdetected at set-pace affordance 1240A in the scrollable list ofaffordances 1240, user interface 1210 can be displayed, as depicted inFIG. 12AF.

FIG. 12AF again illustrates user interface 1210. User interface 1210 canbe displayed in response to selection of set-pace affordance 1240A. Userinterface 1210 can provide options to change how device 600A operateswhen executing a physical activity tracking function corresponding toaffordance 1206A. Text in pace-alert affordance 1214 (as depicted inFIG. 12AF) has been updated to include an indication of a pace set by auser (e.g., “8′29″/1.00 MI”, as depicted at 1214A). By including “/1.00MI” in the text, pace-alert affordance 1214 can indicate that the pacealert for a physical activity tracking function corresponding toaffordance 1206A will be calculated using a rolling operation, asdiscussed herein.

Referring to FIG. 12AG, user input (e.g., tap input) 1227 is received,where user input 1227 corresponds to selection of back affordance 1212.In accordance with a determination that user input 1227 is detected atback affordance 1212, user interface 1204 can be displayed, as depictedin FIG. 12AH.

Referring to FIG. 12AH, affordance 1206A is updated to include anindication of a pace set by a user (e.g., “8′29″/1.00 MI”, as depictedat 1208B). It should be recognized that multiple affordances in the listof affordances 1206 can include a pace set by a user. In some examples,different affordances in the list of affordances 1206 can includedifferent paces set by a user. In addition, different paces set by auser can be calculated using a different operation (e.g., average orrolling).

FIG. 12AI again illustrates user interface 1204. Referring to FIG. 12AI,user input (e.g., tap input) 1229 is received, where user input 1229corresponds to selection of affordance 1206A. In accordance with adetermination that user input 1229 is detected at affordance 1206A inthe scrollable list of affordances 1206, a physical activity trackingfunction configured for outdoor runs is launched. Launching the physicalactivity tracking function can cause a user interface to be displayed(e.g., user interface 1260A as depicted in FIG. 12AJ).

Referring to FIG. 12AJ, user interface 1260A is displayed in response toselection of affordance 1206A. User interface 1260A displays (e.g.,provides feedback regarding) data detected by device 600A for an outdoorrun. To display the data detected by device 600A, user interface 1250Aincludes representations 1262. In FIG. 12W, representations 1262 includeicon 1262AA (e.g., an animated icon of a running man to represent theoutdoor run), total mileage 1262B (e.g., an indication of a number ofmiles traveled during the outdoor run), total calories 1262C (e.g., anindication of an amount of calories determined to be burned by the userduring the outdoor run), average pace per mile 1262D (e.g., anindication of an average amount of time it has taken for device 600A totravel a mile during the last mile of the outdoor run), total time 1262E(e.g., an indication of a duration of the outdoor run), and BPM 1262F(e.g., a calculated number of beats per minute for a heart of a userwearing device 600A). It should be recognized that, in some examples,user interface 1260A can include more or fewer representations, similarto as depicted in FIG. 12AK and discussed below.

FIG. 12AK illustrates multiple user interfaces 1260. User interfaces1260 can be alternatives for displaying (e.g., providing feedbackregarding) data detected by device 600A for an outdoor run (e.g., analternative to user interface 1250 as depicted in FIG. 12W or userinterface 1260A as depicted in FIG. 12AJ). Each of user interfaces 1260include a different number of representations 1262. For example, userinterface 1260B includes 5 representations 1262, user interface 1260Cincludes 4 representations 1262, and user interface 1260D includes 3representations 1262. Each of user interfaces 1260 are meant to be anexample. It should be recognized that other subsets of representations1262 can be used and/or a different order of representations 1262.

It should also be recognized that icon 1262A can be different dependingupon a number of representations 1262. When there are lessrepresentations 1262 (e.g., user interface 1260C includes lessrepresentations 1262 than user interface 1260B), icon 1262A can bebigger, more detailed, and/or include additional information. Forexample, icon 1262AD in user interface 1260D includes a running man andportion 1264. In some examples, portion 1264 can indicate a percent of adaily goal completed using device 600A. In other examples, portion 1264can indicate a percent of a current workout completed using device 600A.

FIG. 13 is a flow diagram illustrating a method for displaying a userinterface to configure a dataset that is used to calculate a pace usingan electronic device in accordance with some examples. Method 1300 isperformed at a device (e.g., 100, 300, 500, 600A, 600B, 800) with adisplay. Some operations in method 1300 are, optionally, combined, theorders of some operations are, optionally, changed, and some operationsare, optionally, omitted.

As described below, method 1300 provides an intuitive way for displayinga user interface to configure a dataset that is used to calculate apace. The method reduces the cognitive burden on a user for configuringthe dataset to calculate the pace, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to configure a pace faster and more efficientlyconserves power and increases the time between battery charges.

At 1302, the device (e.g., 600A) displays a physical activity rate(e.g., a pace (e.g., a mile pace while running)) user interface (e.g.,1216) including a first setting affordance (e.g., 1218B) and a secondsetting affordance (e.g., 1218C). In some examples, the user interfacefather includes a third affordance (e.g., 1218A) for setting a pace.

At 1304, while displaying the physical activity rate user interface, thedevice (e.g., 600A) receives a first user input (e.g., 1213). In someexamples, the user input is a finger gesture, such as a tap, on eitherthe first or second affordance.

At 1306, in response to receiving the first user input, in accordancewith the first user input corresponding to selection of the firstsetting affordance (e.g., 1213), the device configures a physicalactivity rate calculation to use a first portion of a dataset (e.g.,average).

In some examples, the first portion of the dataset includes all of thedataset (e.g., for an average pace).

At 1308, in further response to receiving the first user input, inaccordance with the first user input corresponding to selection of thesecond setting affordance (e.g., 1221), the device configures a physicalactivity rate calculation to use a second portion of the dataset (e.g.,rolling) different than the first portion. In some examples, the firstportion of the dataset and the second portion of the dataset overlap.Displaying an option to choose between different types of physicalactivity rate calculations provides additionally configurabilityregarding how the device operates. Providing additional control optionswithout cluttering the UI enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some examples, configuring the physical activity calculation to usethe second portion of the dataset includes displaying a second userinterface (e.g., 1230) with a first affordance (e.g., 1232A) and asecond affordance (e.g., 1232B). In such examples while displaying thesecond user interface, the device receives a second user input (e.g.,1223). In response to receiving the second user input, in accordancewith a determination that the second user input is detected at the firstaffordance, the device causes the second portion to be determined basedupon an amount of time. In further response to receiving the second userinput, in accordance with a determination that the second user input isdetected at the second affordance (e.g., 1223), the device causes thesecond portion to be determined based upon an amount of distance.

In some examples, after a physical activity rate is set for a type ofphysical activity and while a physical activity tracking functioncorresponding to the type of physical activity is executing, the devicedetects a current physical activity rate (e.g., 1262D). In response todetecting the current physical activity rate, in accordance with adetermination that the current physical activity rate does not satisfy afirst set of one or more alert criteria, the device forgoes output of afirst alert. In some examples, the first set of one or more alertcriteria includes whether the current physical activity rate is offpace. In some examples, the first alert is a haptic, audio, or visualalert. In further response to detecting the current physical activityrate, in accordance with a determination that the current physicalactivity rate satisfies the first set of one or more alert criteria, thedevice outputs the first alert.

In some examples, after outputting the first alert (e.g., a haptic ouraudio alert), the device receives a third user input. In some examples,the third user input is finger tap or a movement of the device (e.g.,detected using one or more accelerometers), such as a wrist raise. Inresponse to determining that the third user input satisfies a first setof one or more visual alert criteria, the device displays a visual alert(e.g., 1244). In some examples, a criterion of the set of one or morevisual alert criteria is that movement of the device corresponds to awrist raise gesture. The visual alert, in accordance with adetermination that the current physical activity rate is less than thephysical activity rate assigned to the type of physical activity,includes a representation (e.g., FIG. 12Z, 1244) corresponding to beingbelow the physical activity rate assigned to the type of physicalactivity (e.g., the current physical activity pace (e.g., a runningpace) has transitioned from being on or above a target activity pace tobeing below the target activity pace). In some examples, less than iswithin a threshold. The visual alert, in accordance with a determinationthat the current physical activity rate is within a threshold of thephysical activity rate assigned to the type of physical activity,includes a representation (e.g., FIG. 12Y, 1244) corresponding to beingon target for the physical activity rate set assigned to the type ofphysical activity (e.g., the current physical activity pace hastransitioned from being above or below a target activity pace tomatching the target activity pace). The visual alert, in accordance witha determination that the current physical activity rate is more than thephysical activity rate assigned to the type of physical activity,includes a representation (e.g., FIG. 12X, 1244) corresponding to beingabove the physical activity rate assigned to the type of physicalactivity (e.g., the current physical activity pace has transitioned frombeing on or below a target activity pace to being above the targetactivity pace).

In some examples, after displaying the visual alert (e.g., 1244), thedevice receives a fourth user input. In some examples, the fourth userinput is a gesture (e.g., wrist raise gesture, a tap gesture, or thelike) that is detected within a predetermined time since receiving afirst input gesture (e.g., a third user input, described above). Inresponse to determining that the fourth user input satisfies a secondset of one or more visual alert criteria, the device displays a secondvisual alert (e.g., 1250) with additional information not in the firstvisual alert. In some examples, the additional information includesmetrics for a current workout, such as mileage, time, or the like.

In some examples, a current pace is highlighted in the second visualalert.

In some examples, physical activities that are capable of being trackedby the device have animated affordances (e.g., running man animationwith no ring, FIG. 10I) and physical activities that are not capable ofbeing tracked by the device have static affordances. For example, one ormore sensors of the device might not be able to detect that a particularphysical activity is being performed (e.g., a physical activity thatappears, to one or more sensors of the device, to be similar to aroutine physical activity). In such an example, user interfaces with anaffordance corresponding to the particular physical activity can includea static affordance to indicate that the particular physical activity isnot capable of being tracked by the device.

In some examples, prior to displaying the physical activity rate userinterface, the device displays a third user interface (e.g., 1210) witha third affordance (e.g., 1214). In such examples, the device receives afifth user input (e.g., 1214) corresponding to the third affordance,where the physical activity rate user interface (e.g., 1216) isdisplayed in response to receiving the fifth user input. After receivingthe first user input, the device redisplays the third user interface(e.g., 1210), wherein the third affordance (e.g., 1214) in theredisplayed third user interface includes an identification (e.g.,1214A) of whether the physical activity calculation is configured to usethe first portion or the second portion of the dataset, and where thethird affordance did not include the identification before receiving thefirst user input.

In some examples, prior to displaying the third user interface (e.g.,1210), the device displays a fourth user interface (e.g., 1204) with ascrollable list of affordances associated with different physicalactivities, where a fourth affordance (e.g., 1206A) in the scrollablelist includes a fifth affordance (e.g., 1208). In some examples, thefourth affordance is to start an outdoor run workout. In some examples,the fifth affordance is an options button for the fourth affordance. Thedevice receives a sixth user input (e.g., 1201) corresponding toselection of the fifth affordance, where the third user interface (e.g.,1210) is displayed in response to receiving the sixth user input. Afterreceiving the first user input, the device redisplays the fourth userinterface (e.g., 1204), where the fourth affordance (e.g., 1206A) in theredisplayed fourth user interface includes an identification (e.g.,1208B) of whether the physical activity calculation is configured to usethe first portion or the second portion of the dataset, and where thefourth affordance did not include the identification before receivingthe first user input.

In some examples, the fourth affordance (e.g., 1206A) includes anidentification (e.g., 1208B) of a first pace assigned to a physicalactivity corresponding to the fourth affordance, where a sixthaffordance (e.g., 1206B) in the scrollable list includes anidentification of a second pace assigned to a physical activitycorresponding to the sixth affordance, and where the second pace isdifferent from the first pace.

In some examples, the physical activity rate user interface is displayedfurther in response to a physical activity rate being set (as depictedin FIGS. 12I-12N).

Note that details of the processes described above with respect tomethod 1300 (e.g., FIG. 13) are also applicable in an analogous mannerto the methods described above. For example, method 1300 optionallyincludes one or more of the characteristics of the various methodsdescribed below with reference to method 700, method 900, or method1100. For example, the user interface of method 700 can be based upon anumber of pace alerts output that were configured using method 1300. Foranother example, the user interface of method 900 can be based upon anumber of pace alerts output that were configured using method 1300. Foranother example, the user interface of method 1300 can configure a pacethat is then used to determine a boundary of a workout (as provided inmethod 1100). For brevity, these details are not repeated below.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific examples. However, the illustrativediscussions above are not intended to be exhaustive or to limit theinvention to the precise forms disclosed. Many modifications andvariations are possible in view of the above teachings. The exampleswere chosen and described in order to best explain the principles of thetechniques and their practical applications. Others skilled in the artare thereby enabled to best utilize the techniques and various exampleswith various modifications as are suited to the particular usecontemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to increaseinteractions between users. The present disclosure contemplates that insome instances, this gathered data may include personal information datathat uniquely identifies or can be used to contact or locate a specificperson. Such personal information data can include demographic data,location-based data, telephone numbers, email addresses, twitter IDs,home addresses, data or records relating to a user's health or level offitness (e.g., vital signs measurements, medication information,exercise information), date of birth, or any other identifying orpersonal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todisplay representations of the personal information. Accordingly, use ofsuch personal information data enables users to view feedback regardingdata received from other users. Further, other uses for personalinformation data that benefit the user are also contemplated by thepresent disclosure. For instance, health and fitness data may be used toprovide insights into a user's general wellness, or may be used aspositive feedback to individuals using technology to pursue wellnessgoals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplates examplesin which users selectively block the use of, or access to, personalinformation data. That is, the present disclosure contemplates thathardware and/or software elements can be provided to prevent or blockaccess to such personal information data. For example, in the case ofactivity and workout services, the present technology can be configuredto allow users to select to “opt in” or “opt out” of participation inthe collection of personal information data during registration forservices or anytime thereafter. In another example, users can select notto provide activity associated data for activity and/or workoutservices. In yet another example, users can select to limit the lengththat activity associated data is maintained or entirely prohibit thedevelopment of user interfaces described herein. In addition toproviding “opt in” and “opt out” options, the present disclosurecontemplates providing notifications relating to the access or use ofpersonal information. For instance, a user may be notified upondownloading an app that their personal information data will be accessedand then reminded again just before personal information data isaccessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedexamples, the present disclosure also contemplates that the variousexamples can also be implemented without the need for accessing suchpersonal information data. That is, the various examples of the presenttechnology are not rendered inoperable due to the lack of all or aportion of such personal information data. For example, content can beselected and delivered to users by inferring activity based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to theservices described herein, or publicly available information.

What is claimed is:
 1. An electronic device, comprising: a display; oneor more processors; and memory storing one or more programs configuredto be executed by the one or more processors, the one or more programsincluding instructions for: receiving a first user activity data for atime period that corresponds to a first user, the first user activitydata including at least first user activity data for a first time subsetof the time period and first user activity data for a second time subsetof the time period, wherein receiving the first user activity data forthe time period includes detecting, using one or more sensors of theelectronic device, the first user activity data; receiving a second useractivity data for the time period that corresponds to a second user, thesecond user activity data including at least second user activity datafor the first time subset and second user activity data for the secondtime subset; displaying, on the display, a user interface, the userinterface concurrently including: a representation of the first useractivity data for the first time subset; a representation of the firstuser activity data for the second time subset; a first cumulativerepresentation of the first user activity data for the time period,wherein the first cumulative representation of the first user activitydata for the time period is based on at least the first user activitydata for the first time subset and the first user activity data for thesecond time subset, wherein the first cumulative representation isdistinct from the representation of the first user activity data for thefirst time subset and the representation of the first user activity datafor the second time subset, and wherein the first cumulativerepresentation comprises a first numerical value; a representation ofthe second user activity data for the first time subset; arepresentation of the second user activity data for the second timesubset; and a second cumulative representation of the second useractivity data for the time period, wherein the second cumulativerepresentation of the second user activity data for the time period isbased on at least the second user activity data for the first timesubset and the second user activity data for the second time subset,wherein the second cumulative representation is distinct from therepresentation of the second user activity data for the first timesubset and the representation of the second user activity data for thesecond time subset, and wherein the second cumulative representationcomprises a second numerical value; after a completion of a firstactivity competition that includes at least the time period, displayinga competition completion user interface, the competition completion userinterface concurrently including: a representation of the first useractivity data for the completed first activity competition; arepresentation of the second user activity data for the completed firstactivity competition; and a new competition initiation affordance;receiving a first user input corresponding to a selection of the newcompetition initiation affordance; and in response to receiving thefirst user input, initiating a process for a second activity competitionbetween the first user and the second user.
 2. The electronic device ofclaim 1, wherein the user interface further includes a representation ofa number of remaining time subsets in the time period.
 3. The electronicdevice of claim 1, wherein the representation of the first user activitydata for the first time subset is adjacent to the representation of thesecond user activity data for the first time subset.
 4. The electronicdevice of claim 1, wherein displaying the user interface furtherincludes: in accordance with a determination that a first valuecorresponding to the first cumulative representation of the first useractivity data exceeds a second value corresponding to the secondcumulative representation of the second user activity data, visuallyemphasizing the first cumulative representation of the first useractivity data for the time period; and in accordance with adetermination that the second value exceeds the first value, visuallyemphasizing the second cumulative representation of the second useractivity data for the time period.
 5. The electronic device of claim 1,wherein receiving the second user activity data includes receiving thesecond user activity data from an external electronic device, the one ormore programs further including instructions for: in response toreceiving the second user activity data from the external electronicdevice, outputting an activity notification, wherein the activitynotification is outputted prior to displaying the user interface.
 6. Theelectronic device of claim 1, wherein the one or more programs furtherinclude instructions for: while displaying the user interface, receivinga second user input corresponding to a request to display additionalinformation corresponding to the first user activity data or the seconduser activity data; and in response to receiving the second user input,displaying a second user interface including additional informationcorresponding to the first user activity data or the second useractivity data, wherein the additional information was not included inthe user interface.
 7. The electronic device of claim 6, wherein the oneor more programs further include instructions for: while displaying theuser interface, receiving a third user input corresponding to a requestto display a messaging user interface for sending a message to anexternal electronic device; and in response to receiving the third userinput, displaying the messaging user interface.
 8. The electronic deviceof claim 1, wherein the one or more programs further includeinstructions for: receiving a third user activity data for the timeperiod that corresponds to a third user, the third user activity dataincluding at least third user activity data for the first time subsetand third user activity data for the second time subset, wherein thethird user activity data is different from the first user activity dataand different from the second user activity data; prior to displayingthe user interface, displaying an activity summary notification, theactivity summary notification including: a first notification elementbased on the first user activity data or the second user activity data;and a second notification element based on at least the third useractivity data.
 9. The electronic device of claim 1, wherein the firstuser activity data corresponds to the first user, wherein the seconduser activity data corresponds to the second user, and wherein the userinterface further includes a representation based on a comparison ofactivity data for the first user and the second user for one or moreprevious time periods, preceding the time period.
 10. The electronicdevice of claim 1, wherein the first cumulative representation is atotal sum of the first user activity data for the time period, andwherein the second cumulative representation is a total sum of thesecond user activity data for the time period.
 11. The electronic deviceof claim 1, wherein the representation of the first user activity datafor the first time subset is displayed adjacent to the representation ofthe second user activity data for the first time subset, withoutdisplaying any interceding representations of activity data for othertime subsets of the time period between the representation of the firstuser activity data for the first time subset and the representation ofthe second user activity data for the first time subset.
 12. Theelectronic device of claim 1, wherein the first user activity datacorresponds to the first user and the second user activity datacorresponds to the second user, and wherein a process for a firstactivity competition between the first user and the second user isinitiated, the one or more programs further including instructions for:displaying an activity status notification, wherein the activity statusnotification includes the user interface.
 13. The electronic device ofclaim 12, the one or more programs further including instructions for:displaying the activity status notification at one or more predefinedtimes during the first activity competition.
 14. The electronic deviceof claim 1, wherein the user interface further includes: arepresentation of a third time subset of the time period for the firstuser, wherein the third time subset has not occurred, wherein therepresentation is displayed as a value of zero; and a representation ofthe third time subset of the time period for the second user, whereinthe third time subset has not occurred, wherein the representation isdisplayed as a value of zero.
 15. A method, comprising: at an electronicdevice including a display: receiving a first user activity data for atime period that corresponds to a first user, the first user activitydata including at least first user activity data for a first time subsetof the time period and first user activity data for a second time subsetof the time period, wherein receiving the first user activity data forthe time period includes detecting, using one or more sensors of theelectronic device, the first user activity data; receiving a second useractivity data for the time period that corresponds to a second user, thesecond user activity data including at least second user activity datafor the first time subset and second user activity data for the secondtime subset; displaying, on the display, a user interface, the userinterface concurrently including: a representation of the first useractivity data for the first time subset; a representation of the firstuser activity data for the second time subset; a first cumulativerepresentation of the first user activity data for the time period,wherein the first cumulative representation of the first user activitydata for the time period is based on at least the first user activitydata for the first time subset and the first user activity data for thesecond time subset, wherein the first cumulative representation isdistinct from the representation of the first user activity data for thefirst time subset and the representation of the first user activity datafor the second time subset, and wherein the first cumulativerepresentation comprises a first numerical value; a representation ofthe second user activity data for the first time subset; arepresentation of the second user activity data for the second timesubset; and a second cumulative representation of the second useractivity data for the time period, wherein the second cumulativerepresentation of the second user activity data for the time period isbased on at least the second user activity data for the first timesubset and the second user activity data for the second time subset,wherein the second cumulative representation is distinct from therepresentation of the second user activity data for the first timesubset and the representation of the second user activity data for thesecond time subset, and wherein the second cumulative representationcomprises a second numerical value; after a completion of a firstactivity competition that includes at least the time period, displayinga competition completion user interface, the competition completion userinterface concurrently including: a representation of the first useractivity data for the completed first activity competition; arepresentation of the second user activity data for the completed firstactivity competition; and a new competition initiation affordance;receiving a first user input corresponding to a selection of the newcompetition initiation affordance; and in response to receiving thefirst user input, initiating a process for a second activity competitionbetween the first user and the second user.
 16. The method of claim 15,wherein the user interface further includes a representation of a numberof remaining time subsets in the time period.
 17. The method of claim15, wherein the representation of the first user activity data for thefirst time subset is adjacent to the representation of the second useractivity data for the first time subset.
 18. The method of claim 15,wherein displaying the user interface further includes: in accordancewith a determination that a first value corresponding to the firstcumulative representation of the first user activity data exceeds asecond value corresponding to the second cumulative representation ofthe second user activity data, visually emphasizing the first cumulativerepresentation of the first user activity data for the time period; andin accordance with a determination that the second value exceeds thefirst value, visually emphasizing the second cumulative representationof the second user activity data for the time period.
 19. The method ofclaim 15, wherein receiving the second user activity data includesreceiving the second user activity data from an external electronicdevice, the method further including: in response to receiving thesecond user activity data from the external electronic device,outputting an activity notification, wherein the activity notificationis outputted prior to displaying the user interface.
 20. The method ofclaim 15, further comprising: while displaying the user interface,receiving a second user input corresponding to a request to displayadditional information corresponding to the first user activity data orthe second user activity data; and in response to receiving the seconduser input, displaying a second user interface including additionalinformation corresponding to the first user activity data or the seconduser activity data, wherein the additional information was not includedin the user interface.
 21. The method of claim 20, further comprising:while displaying the user interface, receiving a third user inputcorresponding to a request to display a messaging user interface forsending a message to an external electronic device; and in response toreceiving the third user input, displaying the messaging user interface.22. The method of claim 15, further comprising: receiving a third useractivity data for the time period that corresponds to a third user, thethird user activity data including at least third user activity data forthe first time subset and third user activity data for the second timesubset, wherein the third user activity data is different from the firstuser activity data and different from the second user activity data;prior to displaying the user interface, displaying an activity summarynotification, the activity summary notification including: a firstnotification element based on the first user activity data or the seconduser activity data; and a second notification element based on at leastthe third user activity data.
 23. The method of claim 15, wherein thefirst user activity data corresponds to the first user, wherein thesecond user activity data corresponds to the second user, and whereinthe user interface further includes a representation based on acomparison of activity data for the first user and the second user forone or more previous time periods, preceding the time period.
 24. Themethod of claim 15, wherein the first cumulative representation is atotal sum of the first user activity data for the time period, andwherein the second cumulative representation is a total sum of thesecond user activity data for the time period.
 25. The method of claim15, wherein the representation of the first user activity data for thefirst time subset is displayed adjacent to the representation of thesecond user activity data for the first time subset, without displayingany interceding representations of activity data for other time subsetsof the time period between the representation of the first user activitydata for the first time subset and the representation of the second useractivity data for the first time subset.
 26. The method of claim 15,wherein the first user activity data corresponds to the first user andthe second user activity data corresponds to the second user, andwherein a process for a first activity competition between the firstuser and the second user is initiated, the method further including:displaying an activity status notification, wherein the activity statusnotification includes the user interface.
 27. The method of claim 26,the method further including: displaying the activity statusnotification at one or more predefined times during the first activitycompetition.
 28. The method of claim 15, wherein the user interfacefurther includes: a representation of a third time subset of the timeperiod for the first user, wherein the third time subset has notoccurred, wherein the representation is displayed as a value of zero;and a representation of the third time subset of the time period for thesecond user, wherein the third time subset has not occurred, wherein therepresentation is displayed as a value of zero.
 29. A non-transitorycomputer-readable storage medium storing one or more programs configuredto be executed by one or more processors of an electronic device with adisplay, the one or more programs including instructions for: receivinga first user activity data for a time period that corresponds to a firstuser, the first user activity data including at least first useractivity data for a first time subset of the time period and first useractivity data for a second time subset of the time period, whereinreceiving the first user activity data for the time period includesdetecting, using one or more sensors of the electronic device, the firstuser activity data; receiving a second user activity data for the timeperiod that corresponds to a second user, the second user activity dataincluding at least second user activity data for the first time subsetand second user activity data for the second time subset; displaying, onthe display, a user interface, the user interface concurrentlyincluding: a representation of the first user activity data for thefirst time subset; a representation of the first user activity data forthe second time subset; a first cumulative representation of the firstuser activity data for the time period, wherein the first cumulativerepresentation of the first user activity data for the time period isbased on at least the first user activity data for the first time subsetand the first user activity data for the second time subset, wherein thefirst cumulative representation is distinct from the representation ofthe first user activity data for the first time subset and therepresentation of the first user activity data for the second timesubset, and wherein the first cumulative representation comprises afirst numerical value; a representation of the second user activity datafor the first time subset; a representation of the second user activitydata for the second time subset; and a second cumulative representationof the second user activity data for the time period, wherein the secondcumulative representation of the second user activity data for the timeperiod is based on at least the second user activity data for the firsttime subset and the second user activity data for the second timesubset, wherein the second cumulative representation is distinct fromthe representation of the second user activity data for the first timesubset and the representation of the second user activity data for thesecond time subset, and wherein the second cumulative representationcomprises a second numerical value; after a completion of a firstactivity competition that includes at least the time period, displayinga competition completion user interface, the competition completion userinterface concurrently including: a representation of the first useractivity data for the completed first activity competition; arepresentation of the second user activity data for the completed firstactivity competition; and a new competition initiation affordance;receiving a first user input corresponding to a selection of the newcompetition initiation affordance; and in response to receiving thefirst user input, initiating a process for a second activity competitionbetween the first user and the second user.
 30. The non-transitorycomputer readable storage medium of claim 29, wherein the user interfacefurther includes a representation of a number of remaining time subsetsin the time period.
 31. The non-transitory computer readable storagemedium of claim 29, wherein the representation of the first useractivity data for the first time subset is adjacent to therepresentation of the second user activity data for the first timesubset.
 32. The non-transitory computer readable storage medium of claim29, wherein displaying the user interface further includes: inaccordance with a determination that a first value corresponding to thefirst cumulative representation of the first user activity data exceedsa second value corresponding to the second cumulative representation ofthe second user activity data, visually emphasizing the first cumulativerepresentation of the first user activity data for the time period; andin accordance with a determination that the second value exceeds thefirst value, visually emphasizing the second cumulative representationof the second user activity data for the time period.
 33. Thenon-transitory computer readable storage medium of claim 29, whereinreceiving the second user activity data includes receiving the seconduser activity data from an external electronic device, the one or moreprograms further including instructions for: in response to receivingthe second user activity data from the external electronic device,outputting an activity notification, wherein the activity notificationis outputted prior to displaying the user interface.
 34. Thenon-transitory computer readable storage medium of claim 29, wherein theone or more programs further include instructions for: while displayingthe user interface, receiving a second user input corresponding to arequest to display additional information corresponding to the firstuser activity data or the second user activity data; and in response toreceiving the second user input, displaying a second user interfaceincluding additional information corresponding to the first useractivity data or the second user activity data, wherein the additionalinformation was not included in the user interface.
 35. Thenon-transitory computer readable storage medium of claim 34, wherein theone or more programs further include instructions for: while displayingthe user interface, receiving a third user input corresponding to arequest to display a messaging user interface for sending a message toan external electronic device; and in response to receiving the thirduser input, displaying the messaging user interface.
 36. Thenon-transitory computer readable storage medium of claim 29, wherein theone or more programs further include instructions for: receiving a thirduser activity data for the time period that corresponds to a third user,the third user activity data including at least third user activity datafor the first time subset and third user activity data for the secondtime subset, wherein the third user activity data is different from thefirst user activity data and different from the second user activitydata; prior to displaying the user interface, displaying an activitysummary notification, the activity summary notification including: afirst notification element based on the first user activity data or thesecond user activity data; and a second notification element based on atleast the third user activity data.
 37. The non-transitory computerreadable storage medium of claim 29, wherein the first user activitydata corresponds to the first user, wherein the second user activitydata corresponds to the second user, and wherein the user interfacefurther includes a representation based on a comparison of activity datafor the first user and the second user for one or more previous timeperiods, preceding the time period.
 38. The non-transitory computerreadable storage medium of claim 29, wherein the first cumulativerepresentation is a total sum of the first user activity data for thetime period, and wherein the second cumulative representation is a totalsum of the second user activity data for the time period.
 39. Thenon-transitory computer readable storage medium of claim 29, wherein therepresentation of the first user activity data for the first time subsetis displayed adjacent to the representation of the second user activitydata for the first time subset, without displaying any intercedingrepresentations of activity data for other time subsets of the timeperiod between the representation of the first user activity data forthe first time subset and the representation of the second user activitydata for the first time subset.
 40. The non-transitory computer readablestorage medium of claim 29, wherein the first user activity datacorresponds to the first user and the second user activity datacorresponds to the second user, and wherein a process for a firstactivity competition between the first user and the second user isinitiated, the one or more programs further including instructions for:displaying an activity status notification, wherein the activity statusnotification includes the user interface.
 41. The non-transitorycomputer readable storage medium of claim 40, the one or more programsfurther including instructions for: displaying the activity statusnotification at one or more predefined times du ring the first activitycompetition.
 42. The non-transitory computer readable storage medium ofclaim 29, wherein the user interface further includes: a representationof a third time subset of the time period for the first user, whereinthe third time subset has not occurred, wherein the representation isdisplayed as a value of zero; and a representation of the third timesubset of the time period for the second user, wherein the third timesubset has not occurred, wherein the representation is displayed as avalue of zero.